my server and 1017

[Parn12]

Hello. I know, everyone is sick of hearin about 1017 error. but i have a quick question. my friend made a server and i am able to connect to it, infact anyone can, but him! when he tries to connect to it, it gives him the 1017 error. no he is running the world and zones on puter 1, and he tries to connect on puter 2, using the eqemu patcher. any ideas? thx for the help

Parn :)

[Ruskin]

IF hes on the internal LAN useing NAT to get to the internet and peeps can connect from outside, then he has a routing isssue with DNS. the easyest way round this is to add lines to the hosts file on the local PC to override DNS and point him straight at the PC on the internal LAN.

DO a search on the local PC, you will find 2 files Hosts and lmhosts under the windows dir. update these with the INTERNAL IP address and name of the server running EQemu.

hope that helps.

Ruskin

[enigmafyv]

Well actually I'm the person who's having the problem. I asked Parn to post, seeing how I was having problems with the forum recently. My issue is:

My EQ Server is my router for my client pc. So I host on (server) and also route for the rest of my computers (clients). Now everyone else can connect to my server accept me on my (client) computer. I've updated my lmhost to show:


...
# The following example illustrates all of these extensions:
#
# 102.54.94.97 rhino #PRE #DOM:networking #net group's DC
# 102.54.94.102 "appname \0x14" #special app server
# 102.54.94.123 popular #PRE #source server
# 102.54.94.117 localsrv #PRE #needed for the include
#
# #BEGIN_ALTERNATE
# #INCLUDE \\localsrv\public\lmhosts
# #INCLUDE \\rhino\public\lmhosts
# #END_ALTERNATE
#
# In the above example, the "appname" server contains a special
# character in its name, the "popular" and "localsrv" server names are
# preloaded, and the "rhino" server name is specified so it can be used
# to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"
# system is unavailable.
#
# Note that the whole file is parsed including comments on each lookup,
# so keeping the number of comments to a minimum will improve performance.
# Therefore it is not advisable to simply add lmhosts file entries onto the
# end of this file.


192.168.0.1 homesvr #PRE
68.117.138.206 homesvr #PRE

My host file says:

# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

127.0.0.1 localhost
192.168.0.1 homesvr
68.117.138.206 homesvr

I'm pretty sure I set it up right, but I'm still not able to connect! What should I do?? I've been looking all over the forum!