Internode WoW Gateway Full Release v2 01/2010

[sorgan]

i seem to be getting an error "Network error: Permission denied"
anyone have any idea how to fix this (putty is giving me the error)

ok i fixed that issue even though i adjusted my firewall to allow it it wasn't now the next issue i have is when i try and load WoW by double clicking on the icon in freecap it does not load any ideas?

[xdneon]

I just came back to wow after about 6 months away, tried to use the gateway but no luck. Is it not functional anymore or something? i am using ports 4000, 6112-6114, 3724, i enter my login info, it says success then just sits there, it doesn't seem to be able to connect to a realm.

[Xeni]

This is a random problem I have encountered now and then myself. It's strange. My husband and I are on the same connection and sometimes it will happen to him and not to me or visa versa. We generally just restart the computer and try again, or sit for a couple of minutes and it will decide to work. This is also without using putty or anything. I haven't used the gateway before.

On the topic of the gateway though, someone just put me onto it. I just installed it, and got to load the game from Freecap, and nothing happens. The very first time, the game just crashed straight away, but it does warn you this can happen. So, I closed that down and tried again. Now, nothing happens. My computer things for a second, and then just nothing. No errors, so crashes, no game loads. Just nothing. However, if I go to load it the old way from the launcher, it will load fine. Is there something I can do to get it to load from Freecap? It has to load via Freecap to be active in the gateway correct? (Sorry, complete nub at this type of thing). Fyi, running Windows 7 64-bit Home Premium.

[Linxus]

Freecap does have its issues at times with 64 bit systems. One solution is to use Proxifier (a one time cost is involved). I use that program and the ssh gateway instead of putty - see the following link for my setup:

http://games.on.net/forums/viewtopic.php?f=122&t=172179&p=2401400&hilit=proxifier#p2401400

Marshy's post below it has another package that works.

[KarmaSutra]

Have Blizzard changed some things recently, I don't recall seeing this before:-

[09.20 19:22:54] Wow.exe - enus.patch.battle.net:1119 error : Could not connect through proxy 127.0.0.1:1080 - Proxy server cannot establish a connection with the target - connection not allowed by ruleset.
[09.20 19:22:56] Wow.exe - ak.worldofwarcraft.com.edgesuite.net:80 error : Could not connect through proxy 127.0.0.1:1080 - Proxy server cannot establish a connection with the target - connection not allowed by ruleset.
^^ Second line repeats 10 or so times.

[XStatic]

That's the wow client trying to connect to the servers to download patches. It looks like you are using proxifier, I would set the settings as follows:

Profile > proxy rules, add wow.exe and direct it to your wowgw as you already are....

Then change the target ports to just 3724. This is the port the wow servers run on, if you set it to only divert 3724 thru the wowgateway everything else will perform as expected and you won't have any errors.

I have however noticed that the wowgw does nothing for my latency at all. 228ms either way. Friends using battleping get under 200.

[KarmaSutra]

Ah of course, it's been a while since I first installed it.

Thanks :o)

[TheScream]

I'm having issues trying to run ProxyCap in SSH mode using the gateway.

Type: SSH
Hostname: wowgw1.internode.on.net
Port: 2222

Proxy Requires Authentication ?
Username: ?
Password: ?
(password is required by ProxyCap)

If I have Requires Authentication unticked, I get the following error:
"SSH client error SSH server disconnected."

If I have Requires Authentication ticked, I get this error:
"SSH client error Authentication failed."

I know I could probably run it in SOCKS mode, but tests show the SSH method reduces ping further.

[thetravellor]

Hi, Does the gateway still work? Does this solution work on Windows 7 x64?

I have tried setting it up today with Wow 4.3 on Windows 7 x64 - followed the instructions at the beginning of this post. Wow crashes soon after double clicking on the icon in Freecap.

[thetravellor]

The gateway seems slower than running without this putty / proxifier combo.

I am running Windows 7 x64.

I have found that modifying the run.bat to load proxifier first makes it work better.

Oh, and the default directory should be c:\wowgw, or you will need to modify settings and the batch script

I can login and run game via Proxifier, but continually get this message about port 3141:

[18:38]
[18:38] Welcome to Proxifier Portable Edition v2.91
[18:38]
[18:41] Wow.exe - 12.129.242.21:80 open
[18:41] Wow.exe - 12.129.242.21:80 open
[18:41] Wow.exe - 12.129.222.54:80 open
[18:41] Wow.exe - 12.129.206.130:1119 open
[18:41] Wow.exe - 12.129.255.44:3724 open
[18:41] Wow.exe - 12.129.255.47:3724 open
[18:41] Wow.exe - 12.129.255.44:3724 close, 530 bytes sent, 1746 bytes (1.70 KB) received
[18:41] Wow.exe - 12.129.222.54:80 close, 281 bytes sent, 252 bytes received
[18:41] Wow.exe - 12.129.242.21:80 close, 283 bytes sent, 415 bytes received
[18:41] Wow.exe - 12.129.242.21:80 close, 268 bytes sent, 552 bytes received
[18:41] Error : the proxy server 127.0.0.1:1080 cannot establish connection to 127.0.0.1:3141
[18:41] Wow.exe - Could not connect to 127.0.0.1:3141 through the proxy server.
[18:41] Wow.exe - 12.129.255.45:3724 open
[18:41] Error : the proxy server 127.0.0.1:1080 cannot establish connection to 127.0.0.1:3141
[18:41] Wow.exe - Could not connect to 127.0.0.1:3141 through the proxy server.
[18:41] Error : the proxy server 127.0.0.1:1080 cannot establish connection to 127.0.0.1:3141
[18:41] Wow.exe - Could not connect to 127.0.0.1:3141 through the proxy server.
[18:41] Error : the proxy server 127.0.0.1:1080 cannot establish connection to 127.0.0.1:3141
[18:41] Wow.exe - Could not connect to 127.0.0.1:3141 through the proxy server.
[18:41] Error : the proxy server 127.0.0.1:1080 cannot establish connection to 127.0.0.1:3141
[18:41] Wow.exe - Could not connect to 127.0.0.1:3141 through the proxy server.
[18:41] Error : the proxy server 127.0.0.1:1080 cannot establish connection to 127.0.0.1:3141
[18:41] Wow.exe - Could not connect to 127.0.0.1:3141 through the proxy server.

[Angeredsoul]

Have Blizzard changed some things recently, I don't recall seeing this before:-

[09.20 19:22:54] Wow.exe - enus.patch.battle.net:1119 error : Could not connect through proxy 127.0.0.1:1080 - Proxy server cannot establish a connection with the target - connection not allowed by ruleset.
[09.20 19:22:56] Wow.exe - ak.worldofwarcraft.com.edgesuite.net:80 error : Could not connect through proxy 127.0.0.1:1080 - Proxy server cannot establish a connection with the target - connection not allowed by ruleset.
^^ Second line repeats 10 or so times.

getting similiar error coming up as well as this error in proxycap "connection not allowed by ruleset (2)

Using proxycap.

127.0.0.1
1080

etc etc

[Submariner]

Anyone know why I would be getting - Network error: reset by peer? Was working great until last 4.3 patch but now get booted out of game, randomly, with that network error.

[danneracci]

Also getting the port 3141 error spam.

WoW.exe - localhost:3141 error : Could not connect through proxy 127.0.0.1:1080 - Proxy server cannot establish a connection with the target - connection not allowed by ruleset.


I think it is causing the game to lag out after a while.
I have tried specifically allowing port 3141 and disabling the background downloading from the launcher.

[Stayna]

Tunnel is stable with Proxifier 3.0 and Putty

Open ports

3724,6112,6113,6114,4000

should help with your errors

------------------------------------------------------------------------------
http://games.on.net/forums/viewtopic.php?p=2309277#p2309277

for how to set up proxifier
------------------------------------------------------------------------------

[Submariner]

Since the last patch I have been getting crazy amounts of lag with the node tunnel, according to WoWs lagometer. Without the tunnel I am now getting 200ms -210ms on average?