3-Day Quickhost Game Cradle of Metal - Running

[En Forcer]

That is a possibility. I have zonealarm running.

I will try setting that URL/IP as a "friend" and allow total access to it to see if that enables my connection.

**I also have Spybot 1.3 running which blocks ad-ware and scrubs for cookies and adware programs and marketing tracking software. I wonder if that program would also interfere with dom2?

[Kel]

I use spybot and adaware, among other things. They have not caused me any problems with Dom2.

- Kel

[deccan]

archaeolept said:
his name is mose not mo

80.161.86.108

also, for convenience's sake w/ network games, it is worth creating a desktop shortcut.

for instance, I would have a shortcut entitled "hard_slog" (the name of the game) w/ this under "properties" (right click shortcut icon to edit properties):

E:\games\dominions2\dom2.exe --tcpclient --ipadr 80.161.86.108 --port 2281-m --res 1152 864 --clickvol 0

where you would replace your own path to the Dom2 executible, the correct port, and the resolution you would like the window to be in (or just ignore all that if you don't want it windowed).

Hey that's a neat idea. I've been keeping server names / port numbers on slips of paper. Thanks.

[En Forcer]

I am unable to connect to the mosehansen server.

I'll have to bail out of this game and wait till some other time.

So...Machaka is free.

I've tried everything. Even the shortcut above but then it tries to connect and the game shuts down.

Should I wipe the game and reinstall?

Also, I am running 2.13

would that bork the connection?

This sucks....

[Cainehill]

You might try disabling zonealarm temporarily, just to see if that's it. I'm running ZA myself, but I think all I had to do is tell ZA that yes, the dom2.exe was to be allowed to access the internet.

Mmm - if you're running in full screen mode, you might be getting blocked by zonealarm but unable to see it.

Edit: Illwinter has written that 2.13 and 2.12 are compatible, so that shouldn't be it. However, if you do succeed in connecting, you really REALLY want to set yourself up with a 2.12 executable for the game; otherwise the battles you watch are likely to be completely hallucinatory.

IE: You watch a battle, see your pretender destroy the opposing enemy with minimal losses. But the battle report says all your guys died, and your Pretender is waiting to be recalled, like a defective appliance.

[Kel]

En Forcer said:
Also, I am running 2.13

would that bork the connection?

Dunno but hopefully it would

I believe he is running 2.12
You might try conencting with 2.12

- Kel

[Thufir]

Kel said:

Dunno but hopefully it would

I believe he is running 2.12
You might try conencting with 2.12

- Kel

It's worth a shot, but it's pretty unlikely that this the problem. I tested hitting Sheap's server w/ a 2.13 client, and got through fine.

[En Forcer]

Cainehill-yeah I tried a bunch of different ways with everything shut off that was running when I went Online. I shut off ZA and spybot and everything but no difference. I might try wiping and reinstalling this weekend.

In the meantime, does anyone have a different IP I can plug in to see if I can connect to a different server?

[DragonFire11]

Hi. I'll play Atlantis since it still seems open. Thanks.

[Cainehill]

En Forcer said:
Cainehill-yeah I tried a bunch of different ways with everything shut off that was running when I went Online. I shut off ZA and spybot and everything but no difference. I might try wiping and reinstalling this weekend.

In the meantime, does anyone have a different IP I can plug in to see if I can connect to a different server?

Mmm - Sheap is the other big hoster (big, juicy, mutton!) I can think of. I could give an IP, but unless he (or someone else) sets up a test game for you to try to connect to (because of passwords, etc), I'm not sure it would help.

Eh - have you tried pinging / tracerouting / telneting? I don't think it'd be a DNS problem, but it could be, or a routing problem, and those would help figure out if it was.

Good luck.

Edit: Oh, and remember: if ZoneAlarm was on at boot, shutting it down may leave the internet shut down. (This is mostly, and definately, true when the vector engine doesn't initalize properly.) In which case, make sure you can get to other pieces of the net. If you can - you're shafted. If you can't - it might be ZA, and rebooting with it turned off might fix it.

Again, good luck.