Forums » General
New
Lo guys new to vendetta tonight..... downloaded and patched ok.........im on a trial account..... but cant login keep getting server timmed out.....anyone else having this or is it just me?...........Or have i missed something?
it could be...............that you need to check your.............connection to the.............internet..........are you able to log in.............? if you are...........and then it says disconnected............then it could be a problem with the game.......
Lo m8 thx for reply my connections fine gets to login screen then connection terminated ..i have shut my firewall down just cant seem to connect to the server
Just checking thu site is there a free trial at the moment?
your account gets 8 free hours automatic
Ok thx for info still cant seem to be able to login
Odd as i down loaded and patched ok
Odd as i down loaded and patched ok
What OS do you use? Under Linux or Mac OS, open a console & run:
traceroute -I majikthise.guildsoftware.com
Under Windows open a command prompt and run:
tracert majikthise.guildsoftware.com
Then post what it outputs here. That'll help troubleshoot whether or not you have a route to the game server.
Also, you did say that you already shut your firewall down, but you might want to double check that, the vast majority of connection problems end up being caused by firewalls blocking the connection. I'm currently logged in just fine, so the game server is up and running.
traceroute -I majikthise.guildsoftware.com
Under Windows open a command prompt and run:
tracert majikthise.guildsoftware.com
Then post what it outputs here. That'll help troubleshoot whether or not you have a route to the game server.
Also, you did say that you already shut your firewall down, but you might want to double check that, the vast majority of connection problems end up being caused by firewalls blocking the connection. I'm currently logged in just fine, so the game server is up and running.
Tracing route to majikthise.guildsoftware.com [204.11.209.42]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.254.254
2 19 ms 19 ms 21 ms lo1-lon3-adsl21.nildram.net [195.112.5.30]
3 18 ms 18 ms 19 ms lon3-14.nildram.net [84.12.224.25]
4 19 ms 20 ms 18 ms lon1-9.nildram.net [84.12.224.14]
5 19 ms 20 ms 18 ms 195.66.224.185
6 88 ms 88 ms 89 ms p10-0.core01.bos01.atlas.cogentco.com [130.117.0
.46]
7 103 ms 102 ms 102 ms p6-0.core01.cle01.atlas.cogentco.com [66.28.4.19
0]
8 112 ms 111 ms 110 ms p3-0.ca01.mke01.atlas.cogentco.com [154.54.1.46]
9 111 ms 111 ms 112 ms 38.112.26.190
10 112 ms 111 ms 111 ms 204.11.209.42
Trace complete.
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.254.254
2 19 ms 19 ms 21 ms lo1-lon3-adsl21.nildram.net [195.112.5.30]
3 18 ms 18 ms 19 ms lon3-14.nildram.net [84.12.224.25]
4 19 ms 20 ms 18 ms lon1-9.nildram.net [84.12.224.14]
5 19 ms 20 ms 18 ms 195.66.224.185
6 88 ms 88 ms 89 ms p10-0.core01.bos01.atlas.cogentco.com [130.117.0
.46]
7 103 ms 102 ms 102 ms p6-0.core01.cle01.atlas.cogentco.com [66.28.4.19
0]
8 112 ms 111 ms 110 ms p3-0.ca01.mke01.atlas.cogentco.com [154.54.1.46]
9 111 ms 111 ms 112 ms 38.112.26.190
10 112 ms 111 ms 111 ms 204.11.209.42
Trace complete.
don't know if it's an issue, but many users have had problems with cogentco...
I see that in your trace route.
I see that in your trace route.
Cogent just gives people worse latency than they ought to have, it doesn't usually cause connections to time out.
That traceroute looks normal, doesn't show any problems. You were able to update, it's just logging in to the game itself that's giving the connection time out, right? The game uses UDP port 21141, connection problems are almost always caused by some firewall somewhere blocking traffic on that port. And where you do have a route to the server, I'd guess it most likely a firewall issue. You did say you tried disabling it, but I'd recommend double checking that.
Also, what operating system do you use? That looked like a Windows trace route, but which version of Windows?
That traceroute looks normal, doesn't show any problems. You were able to update, it's just logging in to the game itself that's giving the connection time out, right? The game uses UDP port 21141, connection problems are almost always caused by some firewall somewhere blocking traffic on that port. And where you do have a route to the server, I'd guess it most likely a firewall issue. You did say you tried disabling it, but I'd recommend double checking that.
Also, what operating system do you use? That looked like a Windows trace route, but which version of Windows?
Sorry to get in late on this.
Beolach is quite right, this is typical of a firewall issue. The XP firewall seems to have a tendency to protect you from yourself and sometimes continues to be active even after being disabled.
You might try logging out of your ISP and closing your connection software, disabling your firewall, then re-connecting to the 'net and the game. You might also try multiple disabling attempts. Once the firewall takes notice of Vendetta, it should prompt for handling instructions.
You could also try manually telling your firewall to allow vendetta.exe and vendetta.rlb
Beolach is quite right, this is typical of a firewall issue. The XP firewall seems to have a tendency to protect you from yourself and sometimes continues to be active even after being disabled.
You might try logging out of your ISP and closing your connection software, disabling your firewall, then re-connecting to the 'net and the game. You might also try multiple disabling attempts. Once the firewall takes notice of Vendetta, it should prompt for handling instructions.
You could also try manually telling your firewall to allow vendetta.exe and vendetta.rlb
You guys know about the problems between L3 and Cogent, right? They had a little spat and disabled their peering. At least now you can see if you're single-homed or multihomed. (For example, I can't pull up photobucket at ALL from Wisconsin)
http://www.infoworld.com/article/05/10/06/HNispspat_1.html
http://ask.slashdot.org/article.pl?sid=05/10/05/2247207
Thanks to Screwball and Beolach for the links...
http://www.infoworld.com/article/05/10/06/HNispspat_1.html
http://ask.slashdot.org/article.pl?sid=05/10/05/2247207
Thanks to Screwball and Beolach for the links...
Note that since banrocc's trace route was able to complete, his connection problem is not caused by the Level3/Cogent issue. In fact, now that I think about it, I'm pretty sure that at least since August, Red Anvil has direct links to both Level3 (through RoadRunner) and Cogent, so no matter if any client is single-homed with either L3 or Cogent, they should still be able to connect. Latency might be worse than usual, though.
Yep. Beolach is right again.
The user profile fits for a firewall issue as well: new or freshly-patched clients are the most prone to the firewall blockage issue. See the Bugs forum for the same problem and seemingly spontaneous resolution. It's his firewall.
The user profile fits for a firewall issue as well: new or freshly-patched clients are the most prone to the firewall blockage issue. See the Bugs forum for the same problem and seemingly spontaneous resolution. It's his firewall.
Update (4:20pm edt): Level 3 has restored all peers with Cogent as of 4:00pm edt. We are seeing some latency in traffic across to Level 3 as sessions re-establish, mail servers deliver messages, etc. We hope the above normal traffic volumes will decrease within the next hour.
So THAT"S why I got ping problems.
So THAT"S why I got ping problems.