Hi all,
I was suggested to download the Gproxy tool for Warcraft III which i did. I followed the guide found here; http://wiki.entgaming.net/index.php?title=EntGaming:GProxyGui. But I want to host a private game, So i exit the proxy go back into choose a server select US west. Connect to battle net, go to host a game and no one can connect. I could host games previously with no issue.
So far to trouble shoot this issue I have re forwarded ports, deleted out the gproxy from selected folder.
I still require some assistance on this issue. I would like to have gproxy removed completely.
Regards
Running Internal Gproxy not allowing me to host games after quitting client
Moderators: Oversight Staff, Processing Staff
-
- Basic Tree
- Posts: 5
- Joined: Sun Jan 04, 2015 1:29 am
- Has thanked: 1 time
-
- Protector of Nature
- Posts: 3160
- Joined: Thu Sep 26, 2013 9:37 pm
- Has thanked: 18 times
- Been thanked: 47 times
Re: Running Internal Gproxy not allowing me to host games after quitting client
Check what port wc3 is using under options->gameplay.
iirc gproxy tends to change it, you should want it to be 6112.
iirc gproxy tends to change it, you should want it to be 6112.
- These users thanked the author Stealer for the post:
- OzziePoison (Thu Jan 29, 2015 5:16 am)
-
- Basic Tree
- Posts: 5
- Joined: Sun Jan 04, 2015 1:29 am
- Has thanked: 1 time
Re: Running Internal Gproxy not allowing me to host games after quitting client
Something as simple as that. Well, thats fixed it. Didnt know it would change my in game port. If I wish to use gproxy again do I have to port forwrd the new port number?
-
- Protector of Nature
- Posts: 3160
- Joined: Thu Sep 26, 2013 9:37 pm
- Has thanked: 18 times
- Been thanked: 47 times
Re: Running Internal Gproxy not allowing me to host games after quitting client
You're going to want to change that number back to 6112 whenever you want to play and you are not using groxy.
iirc gproxy changes it so that the gproxy client can use 6113 (?) to talk to the bot and then it uses that other port to communicate to your wc3 process.
If you don't fix it, when other people try to play with you they might not have that other port 'opened' or allowed or something and so you won't be able to connect since you're using a non-standard port.
iirc gproxy changes it so that the gproxy client can use 6113 (?) to talk to the bot and then it uses that other port to communicate to your wc3 process.
If you don't fix it, when other people try to play with you they might not have that other port 'opened' or allowed or something and so you won't be able to connect since you're using a non-standard port.
Return to “Processed Support Cases”
Who is online
Users browsing this forum: No registered users and 18 guests