_Kerosh_
03-03-2005, 07:24 PM
First off, I am not a noob and I know more than most people do about these issues. I usually help others with connection problems and support.
Ok, now I have never had this problem and I cannot believe I haven't solved it yet. I went to support and no one there could solve this, so I come out to you now to help me.
The Problem:
When I try to login to EverQuest Emulator, I get the special error that says you cannot connect to server, check your internet, etc.
Obviously, many who are experienced in this field would think that the eqhost is the problem, but that was not the case:
eqemulator.net:5994
eqemulator.net:5995
newlogin1.eqemulator.net:5994
newlogin1.eqemulator.net:5995
66.51.156.206:5994
66.51.156.206:5995
I tried all of those. I checked my spacing, no extra spaces. This is what my eqhost file looks like atm:
[LoginServer]
Host=66.51.156.206:5994
I can ping to all of the above and I can trace route to all of the above, I just cannot login.
Now, experienced people would automatically think that the problem is the router, so the next step is obviously pinging and see if it works. I tried this:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\AaronD>ping eqemulator.net
Pinging eqemulator.net [66.51.156.206] with 32 bytes of data:
Reply from 66.51.156.206: bytes=32 time=194ms TTL=51
Reply from 66.51.156.206: bytes=32 time=164ms TTL=51
Reply from 66.51.156.206: bytes=32 time=198ms TTL=51
Reply from 66.51.156.206: bytes=32 time=190ms TTL=51
Ping statistics for 66.51.156.206:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 164ms, Maximum = 198ms, Average = 186ms
C:\Documents and Settings\AaronD>^V
As you can see, the pinging works. The next thing people would guess is Trace Route, so I tried that with UOTrace and cmd Trace.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\AaronD>tracert eqemulator.net
Tracing route to eqemulator.net [66.51.156.206]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.2.1
2 55 ms 14 ms 11 ms 209-94-94-1.amigo.net [209.94.94.1]
3 38 ms 24 ms 36 ms scrmca2wcx1-ser0-1-6.wcg.net [64.200.192.93]
4 29 ms 39 ms 37 ms sntcca1wcx1-pos14-1.wcg.net [64.200.240.113]
5 73 ms 44 ms 29 ms sntcca4lcx1-pos6-0.wcg.net [64.200.240.130]
6 70 ms 50 ms 41 ms so-3-3-0.edge1.SanJose1.Level3.net [4.68.127.29]
7 50 ms 30 ms 35 ms so-1-2-0.bbr2.SanJose1.Level3.net [209.244.3.141
]
8 104 ms 111 ms 109 ms so-0-1-0.mp2.Detroit1.Level3.net [64.159.0.198]
9 137 ms 107 ms 104 ms so-10-0.hsa2.Detroit1.Level3.net [4.68.115.6]
10 105 ms 123 ms 122 ms 4.79.14.6
11 139 ms 103 ms 92 ms t1-customer.123.net [66.103.255.34]
12 135 ms 105 ms 107 ms ns1.eqemulator.net.156.51.66.in-addr.arpa [66.51
.156.206]
Trace complete.
C:\Documents and Settings\AaronD>
As you can all see, there are no problems. When I went into UOTrace, I recieved this:
Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/Ping best/worst
* Unknown Host * 192.168.2.1 1 0ms 0ms 0% 26 / 260ms / 10ms
209-94-94-1.amigo.net 209.94.94.1 2 10ms 11ms 0% 26 / 269ms / 43ms
scrmca2wcx1-ser0-1-6.wcg.net 64.200.192.93 3 32ms 37ms 0% 26 / 2624ms / 88ms
sntcca1wcx1-pos14-1.wcg.net 64.200.240.113 4 39ms 36ms 0% 26 / 2626ms / 90ms
sntcca4lcx1-pos6-0.wcg.net 64.200.240.130 5 32ms 35ms 0% 26 / 2627ms / 61ms
so-3-3-0.edge1.SanJose1.Level3.ne4.68.127.29 6 50ms 38ms 0% 26 / 2627ms / 84ms
so-1-2-0.bbr2.SanJose1.Level3.net209.244.3.141 7 34ms 38ms 0% 26 / 2629ms / 78ms
so-0-1-0.mp2.Detroit1.Level3.net 64.159.0.198 8 103ms 110ms 0% 26 / 26102ms / 192ms
so-10-0.hsa2.Detroit1.Level3.net 4.68.115.6 9 132ms 110ms 0% 26 / 26102ms / 132ms
* Unknown Host * 4.79.14.6 10 116ms 125ms 0% 26 / 26101ms / 351ms
t1-customer.123.net 66.103.255.34 11 97ms 96ms 0% 26 / 2689ms / 110ms
ns1.eqemulator.net.156.51.66.in-a66.51.156.206 12 107ms 98ms 0% 25 / 2588ms / 165ms
As you can all see, it was still fine, my worst number wasn't bad enough to cause intense lagging issues.
The next guess would be the router, but this is fine also:
The private computer for all of these is my own IP address btw.
1. Enabled Blizzard Battle.net
Inbound Port: 6112-6112
Type: UDP
Private Port: 6112-6112
2. Enabled FTP
Inbound Port: 20-21
Type: TCP
Private Port: 20-21
3. Enabled Web
Inbound Port: 80-80
Type: TCP
Private Port: 80-80
4. Enabled MSN Messenger
Inbound Port: 6901-6901
Type: UDP
Private Port: 6901-6901
5. Enabled EverQuest
Inbound Port: 1024-6000
Type: TCP
Private Port: 1024-6000
6. Enabled EverQuest
Inbound Port: 1024-6000
Type: UDP
Private Port: 1024-6000
7. Enabled EverQuest
Inbound Port: 6001-7000
Type: TCP
Private Port: 6001-7000
As some of you can probably tell, my router has pre-set settings for games and online programs. This router was made for online chatting, online gaming, etc. I like it because I work on online games as well as play them. The old one, which was much better (512 meg instead of this 256 meg) could not connect to battle.net no matter what I did. Ports were openned. This one can. It is not a UDP Issue...
So, now that we see that it is not a router issue, what could it be?
Inexperienced people in this field would have first asked 2 questions, patch or eqhost. However, the error for a patch is when it just hangs there. Because I stated that I recieved the connection error, that should be knocked off the list, but for all the beginners in this field, I will sate your curiosity.
Using a program provided by Cisyouc, I found out my EQ Version Number which was:
SHORT VERSION: SEQ12167
LONG VERSION: EQ803157012C78A812C924A7C11E2727A6B8291587
This is the version that works... It means that I did not patch past 12/15/04.
Also, so that other people would be happy, I downloaded the links they provided of eqhost files and used those, still didn't work. It is not patchiing problem or eqhost problem.
Now on to the part where I am stuck. I know what isn't wrong, but I don't know what is wrong. If anyone could help me figure this out, it would be much appreciated. I have a Belkin Router, which is one of the top gaming routers on the market and was referred to by a few college students, so it isn't the router either, I have proof above.
Also, as further proof, I will repeat again, if it were the router I couldn't connect to battle.net, but I can, so it isn't.
I really need help. Please do not ask me about things I have already gone over. All the information and data is up there.
Btw, the only thing I fergot to do that was mentioned in support was trace route, lol : P. I like the EQ Trace Route a lot more than B.net, you don't have to go all over your comp and write log files : D.
Ok, now I have never had this problem and I cannot believe I haven't solved it yet. I went to support and no one there could solve this, so I come out to you now to help me.
The Problem:
When I try to login to EverQuest Emulator, I get the special error that says you cannot connect to server, check your internet, etc.
Obviously, many who are experienced in this field would think that the eqhost is the problem, but that was not the case:
eqemulator.net:5994
eqemulator.net:5995
newlogin1.eqemulator.net:5994
newlogin1.eqemulator.net:5995
66.51.156.206:5994
66.51.156.206:5995
I tried all of those. I checked my spacing, no extra spaces. This is what my eqhost file looks like atm:
[LoginServer]
Host=66.51.156.206:5994
I can ping to all of the above and I can trace route to all of the above, I just cannot login.
Now, experienced people would automatically think that the problem is the router, so the next step is obviously pinging and see if it works. I tried this:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\AaronD>ping eqemulator.net
Pinging eqemulator.net [66.51.156.206] with 32 bytes of data:
Reply from 66.51.156.206: bytes=32 time=194ms TTL=51
Reply from 66.51.156.206: bytes=32 time=164ms TTL=51
Reply from 66.51.156.206: bytes=32 time=198ms TTL=51
Reply from 66.51.156.206: bytes=32 time=190ms TTL=51
Ping statistics for 66.51.156.206:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 164ms, Maximum = 198ms, Average = 186ms
C:\Documents and Settings\AaronD>^V
As you can see, the pinging works. The next thing people would guess is Trace Route, so I tried that with UOTrace and cmd Trace.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\AaronD>tracert eqemulator.net
Tracing route to eqemulator.net [66.51.156.206]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.2.1
2 55 ms 14 ms 11 ms 209-94-94-1.amigo.net [209.94.94.1]
3 38 ms 24 ms 36 ms scrmca2wcx1-ser0-1-6.wcg.net [64.200.192.93]
4 29 ms 39 ms 37 ms sntcca1wcx1-pos14-1.wcg.net [64.200.240.113]
5 73 ms 44 ms 29 ms sntcca4lcx1-pos6-0.wcg.net [64.200.240.130]
6 70 ms 50 ms 41 ms so-3-3-0.edge1.SanJose1.Level3.net [4.68.127.29]
7 50 ms 30 ms 35 ms so-1-2-0.bbr2.SanJose1.Level3.net [209.244.3.141
]
8 104 ms 111 ms 109 ms so-0-1-0.mp2.Detroit1.Level3.net [64.159.0.198]
9 137 ms 107 ms 104 ms so-10-0.hsa2.Detroit1.Level3.net [4.68.115.6]
10 105 ms 123 ms 122 ms 4.79.14.6
11 139 ms 103 ms 92 ms t1-customer.123.net [66.103.255.34]
12 135 ms 105 ms 107 ms ns1.eqemulator.net.156.51.66.in-addr.arpa [66.51
.156.206]
Trace complete.
C:\Documents and Settings\AaronD>
As you can all see, there are no problems. When I went into UOTrace, I recieved this:
Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/Ping best/worst
* Unknown Host * 192.168.2.1 1 0ms 0ms 0% 26 / 260ms / 10ms
209-94-94-1.amigo.net 209.94.94.1 2 10ms 11ms 0% 26 / 269ms / 43ms
scrmca2wcx1-ser0-1-6.wcg.net 64.200.192.93 3 32ms 37ms 0% 26 / 2624ms / 88ms
sntcca1wcx1-pos14-1.wcg.net 64.200.240.113 4 39ms 36ms 0% 26 / 2626ms / 90ms
sntcca4lcx1-pos6-0.wcg.net 64.200.240.130 5 32ms 35ms 0% 26 / 2627ms / 61ms
so-3-3-0.edge1.SanJose1.Level3.ne4.68.127.29 6 50ms 38ms 0% 26 / 2627ms / 84ms
so-1-2-0.bbr2.SanJose1.Level3.net209.244.3.141 7 34ms 38ms 0% 26 / 2629ms / 78ms
so-0-1-0.mp2.Detroit1.Level3.net 64.159.0.198 8 103ms 110ms 0% 26 / 26102ms / 192ms
so-10-0.hsa2.Detroit1.Level3.net 4.68.115.6 9 132ms 110ms 0% 26 / 26102ms / 132ms
* Unknown Host * 4.79.14.6 10 116ms 125ms 0% 26 / 26101ms / 351ms
t1-customer.123.net 66.103.255.34 11 97ms 96ms 0% 26 / 2689ms / 110ms
ns1.eqemulator.net.156.51.66.in-a66.51.156.206 12 107ms 98ms 0% 25 / 2588ms / 165ms
As you can all see, it was still fine, my worst number wasn't bad enough to cause intense lagging issues.
The next guess would be the router, but this is fine also:
The private computer for all of these is my own IP address btw.
1. Enabled Blizzard Battle.net
Inbound Port: 6112-6112
Type: UDP
Private Port: 6112-6112
2. Enabled FTP
Inbound Port: 20-21
Type: TCP
Private Port: 20-21
3. Enabled Web
Inbound Port: 80-80
Type: TCP
Private Port: 80-80
4. Enabled MSN Messenger
Inbound Port: 6901-6901
Type: UDP
Private Port: 6901-6901
5. Enabled EverQuest
Inbound Port: 1024-6000
Type: TCP
Private Port: 1024-6000
6. Enabled EverQuest
Inbound Port: 1024-6000
Type: UDP
Private Port: 1024-6000
7. Enabled EverQuest
Inbound Port: 6001-7000
Type: TCP
Private Port: 6001-7000
As some of you can probably tell, my router has pre-set settings for games and online programs. This router was made for online chatting, online gaming, etc. I like it because I work on online games as well as play them. The old one, which was much better (512 meg instead of this 256 meg) could not connect to battle.net no matter what I did. Ports were openned. This one can. It is not a UDP Issue...
So, now that we see that it is not a router issue, what could it be?
Inexperienced people in this field would have first asked 2 questions, patch or eqhost. However, the error for a patch is when it just hangs there. Because I stated that I recieved the connection error, that should be knocked off the list, but for all the beginners in this field, I will sate your curiosity.
Using a program provided by Cisyouc, I found out my EQ Version Number which was:
SHORT VERSION: SEQ12167
LONG VERSION: EQ803157012C78A812C924A7C11E2727A6B8291587
This is the version that works... It means that I did not patch past 12/15/04.
Also, so that other people would be happy, I downloaded the links they provided of eqhost files and used those, still didn't work. It is not patchiing problem or eqhost problem.
Now on to the part where I am stuck. I know what isn't wrong, but I don't know what is wrong. If anyone could help me figure this out, it would be much appreciated. I have a Belkin Router, which is one of the top gaming routers on the market and was referred to by a few college students, so it isn't the router either, I have proof above.
Also, as further proof, I will repeat again, if it were the router I couldn't connect to battle.net, but I can, so it isn't.
I really need help. Please do not ask me about things I have already gone over. All the information and data is up there.
Btw, the only thing I fergot to do that was mentioned in support was trace route, lol : P. I like the EQ Trace Route a lot more than B.net, you don't have to go all over your comp and write log files : D.