Hello,

I've got a problem with the login. The updater starts normally and I can launch the vendetta application. After typing in my username and password, I get the following message:

Connecting (and some time later)
Connection Terminated: Connection to server timed out.

I tried with and without the firewall, but nothing changes. Do you have any ideas or similar problems?

BTW, I'm running on OSX 10.4.2

Hi, I am currently having no issues logging into the server, but have had this issue a lot in the past. (usually turns out to be my isp, or something in between my isp and vendetta :/)

I'm not mac litterate, so if this isnt usefull, just ignore it, but could you try ping the vendetta game server?

ie, open a terminal and type ping majikthise.guildsoftware.com ? do you get a reply?

[edit]

You could also try make firewall exceptions for the ports used as detailed here http://vendetta-online.com/firewalls.html but in my experience, vendetta just works :)

Ping works like it should:

PING majikthise.guildsoftware.com (204.11.209.42): 56 data bytes
64 bytes from 204.11.209.42: icmp_seq=0 ttl=51 time=125.527 ms
64 bytes from 204.11.209.42: icmp_seq=1 ttl=51 time=124.644 ms

The high latency is because of an upload of a website. The UDP-port 21141 is open on my firewall. But I have this problem with the firewall disabled, too.

Hmm, so you cannot even get to the character select screen right? I wonder if a tracert would reutrn any more info, but again, i dunno how to tracert on a mac :P

maybe its tracert majikthise.guildsoftware.com ?

I'm pretty sure it's traceroute under Macs (as it is under *nix, remember, Mac OS X is a BSD). It's MS Windows where it's tracert.

Note that the traceroute included with Mac OS may or may not support ICMP echo requests, I've hear that some traceroutes under Mac OS X only support UDP datagrams. majikthise.guildsoftware.com will not respond to UDP datagrams exceeding TTL, so you get stuff like this:

$ traceroute majikthise.guildsoftware.com
<snip>
14 p12-0.core03.ord01.atlas.cogentco.com (154.54.3.154) 83.146 ms 81.571 ms 84.983 ms
15 p4-0.ca02.mke01.atlas.cogentco.com (154.54.1.154) 616.448 ms 102.128 ms 107.845 ms
16 38.112.26.190 (38.112.26.190) 90.973 ms 85.295 ms 93.065 ms
17 * * *
18 * * *
19 * * *

Rather than the response that you would get with ICMP echo requests, like this:

$ traceroute -I majikthise.guildsoftware.com
<snip>
14 p12-0.core03.ord01.atlas.cogentco.com (154.54.3.154) 83.403 ms 83.232 ms 83.755 ms
15 p4-0.ca02.mke01.atlas.cogentco.com (154.54.1.154) 1085.066 ms 247.139 ms 294.930 ms
16 38.112.26.190 (38.112.26.190) 87.426 ms 85.640 ms 105.674 ms
17 204.11.209.42 (204.11.209.42) 84.974 ms 85.441 ms 97.066 ms

OK, here's the traceroute output:

„Traceroute“ wurde gestartet…

traceroute to majikthise.guildsoftware.com (204.11.209.42), 64 hops max, 40 byte packets
1 10.0.1.1 (10.0.1.1) 5.975 ms 2.239 ms 1.164 ms
2 dsl-082-083-216-001.arcor-ip.net (82.83.216.1) 239.066 ms 235.785 ms 87.289 ms
3 kln-145-254-9-105.arcor-ip.net (145.254.9.105) 255.038 ms 236.900 ms 240.846 ms
4 ffm-145-254-16-18.arcor-ip.net (145.254.16.18) 231.152 ms 249.189 ms 268.379 ms
5 82.82.0.206 (82.82.0.206) 304.072 ms 250.248 ms 266.471 ms
6 p3-0.core01.ams03.atlas.cogentco.com (130.117.0.145) 394.527 ms 266.368 ms 283.356 ms
7 p5-0.core01.lon02.atlas.cogentco.com (130.117.1.225) 283.593 ms 270.297 ms 275.618 ms
8 p10-0.core01.bos01.atlas.cogentco.com (130.117.0.46) 386.511 ms 346.567 ms 423.529 ms
9 p5-0.core01.ord01.atlas.cogentco.com (66.28.4.110) 327.832 ms 379.231 ms 419.361 ms
10 p11-0.core03.ord01.atlas.cogentco.com (154.54.3.150) 373.996 ms 372.670 ms 359.470 ms
11 p4-0.ca02.mke01.atlas.cogentco.com (154.54.1.154) 405.699 ms 516.448 ms 657.411 ms
12 38.112.26.190 (38.112.26.190) 368.879 ms 365.128 ms 452.671 ms
13 * * *

Guess, this is ok, isn't it?

Sorry for the belated reply, yep, thats fine, its a mystery to me why you cannot login, I can only suggest emailing one of the devs. (or waiting here for a reply)

I hear johns email inbox is a blackhole, but I once got a reply from andy, :P so try andy@guildsoftware.com :)

[Edit]

Yeah, I should have known that Beo, but still, heh.

Now, that's strange ... today, after changing nothing I could log in again. Can't make head nor tail of this. My guess is that some ISP must have changed something.

Anyway guys, thanks a lot for your good advise.

That's really weird. I think you are the 3rd person to have posted a problem and then had a spontaneous recovery. What ISP are you using?

Perhaps it's the Flying Spaghetti Monster at work.

OK, and now I report back with the same problem again. I did update to QT 7.0.2 and iTunes 5.0, but this should not break the connection.

My ISP is Arcor, one of the larger companies in germany. Perhaps the other users are using the same ISP?

This is really mysterious. What the heck are they (my ISP) doing with my bits? Routing them through some kind of filters?

Sorry to have had to ask the obvious before. I did see Arcor in your traceroute but didn't recognize it.

Are you going through any sort of shared business or school router?

No, my Mac uses wlan to connect to the airport express base station. The communication is encrypted by WPA. My DSL-modem is connected to the base station. That's all, a pretty common home use setup.

I don't share this connection with anybody else, it's my private line at home. One thing I noticed is the fact, that whether I type the right or a wrong password, the reaction is the same. I did a reset of the Base Station and the DSL-modem, but this didn't change anything.

OK, this seems to get a monologue:

I've worked through the whole network settings of the WDS System of the Airport Stations and I think I found the culprit. The multicast rate was set to 11. After lowering this to 2 login works again.

To me this sounds reasonable. Sporadic login problem because multicast rate can't be reached due to natural fluctuation of the signal strength. So one hint for all with sporadic login problems: check the multicast rate of your wlan router.

Interesting. That's a new one for me. Be sure to post again if you have further trouble.

I have the same problem after I tried using the /navroute to warp into a sector I should not have.... :(

Can someone reset my location?

I can't connect either tonight. I did connect at lunch time though.

Last I remember, I had docked in UIT space. Nowhere out of the ordinary.

What gives?

Edit: seems like my traceroute stops at my machine. As if I didn't have a network connection. Strange. Let me reboot and we'll see what happens...

Edit2: Nope. Rebooting my machines, router and cable model doesn't help.

Given those messages that were added after mine, this shows it's not at my end (?).

I think them sercos are playing technological warfare again?

zomg this just happent to me too!

omg damn internet is going to the loonies

I was just connected a few hours ago... but now my connection to the server is timing out... Also, connecting to the test server gives a "Protocol version does not match server version" error, which is funky.

Ok, so it's not just me...

My router has been crapping out a lot the past few days so I have been disconnecting a lot in the afternoons... guess this is an excuse for a new log entry, eh? :D

Server issues or intermediate internet hub problems? TPG ship taking all the bandwidth?