[Archive] Help please to put server online 4.3.4 cata
[Archive] Help please to put server online 4.3.4 cata
11-04-2025, 05:12 PM
Original source
Quote:3b799e5388 said:You said you disabled Firewall, but what about your anti-virus entirely? I've had my anti-virus block connections before.
Same here, locally on my pc the game and server runs great.
Connecting externally to my pc is succesful for AUTHSERVER, but fails at connecting to WORLDSERVER.
Port 8085 (worldserver) simply WILL NOT open to external connections, no matter what I configure. (conf files and DB)
Port 3724 (authserver) is opened and accessed succesfully, so port forwarding works.
(I also use port forwarding for other computers and services, which work as well)
using Gibson's ShieldsUp to test multiple ports, I get these results:
3724
OPEN!battlenet
Blizzard Battlenet
8085
StealthUnknown Protocol for this port
Unknown Application for this port
8086
ClosedUnknown Protocol for this port
Unknown Application for this port
in authserver.conf and worldserver.conf I tried binding IP to my external/WAN IP which resulted in error, which is logical as the services run locally, not externally.
in DB "emucoach_v13_vip_auth" > realmlist > data
I tried setting column "address" to external IP as my internal IP, but no success
I disabled Windows Firewall and/or allowed port 3724 and 8085 through.
Using Sysinternals' TCPview, I see that running wow.exe (client) locally, the process connects to both ports.
I use v13 VIP repack Cataclysm 4.3.4 build 15535 and is my first experience with repacks/wow server.
Click to expand...
![[Image: transpixel.gif]](https://www.grc.com/image/transpixel.gif){kind=tracking}
If all else fails, you could just change the port used by worldserver.conf to a different, unused port and see if the connection will be allowed. To do that, just go into worldserver.conf and change the ports used by it, and you might have to change the port in the realmlist.
I think I remember a situation where I opened 8085/6 and it told me the port was closed, yet people could still connect - I doubt that'll help your situation, just a note on the reliability of checking if ports are open/etc.
rektbyfaith
11-04-2025, 05:12 PM #11Archived author: mata1 • Posted: 2025-11-04T18:12:46.019093
Original source
Quote:3b799e5388 said:You said you disabled Firewall, but what about your anti-virus entirely? I've had my anti-virus block connections before.
Same here, locally on my pc the game and server runs great.
Connecting externally to my pc is succesful for AUTHSERVER, but fails at connecting to WORLDSERVER.
Port 8085 (worldserver) simply WILL NOT open to external connections, no matter what I configure. (conf files and DB)
Port 3724 (authserver) is opened and accessed succesfully, so port forwarding works.
(I also use port forwarding for other computers and services, which work as well)
using Gibson's ShieldsUp to test multiple ports, I get these results:
3724
OPEN!battlenet
Blizzard Battlenet
8085
StealthUnknown Protocol for this port
Unknown Application for this port
8086
ClosedUnknown Protocol for this port
Unknown Application for this port
in authserver.conf and worldserver.conf I tried binding IP to my external/WAN IP which resulted in error, which is logical as the services run locally, not externally.
in DB "emucoach_v13_vip_auth" > realmlist > data
I tried setting column "address" to external IP as my internal IP, but no success
I disabled Windows Firewall and/or allowed port 3724 and 8085 through.
Using Sysinternals' TCPview, I see that running wow.exe (client) locally, the process connects to both ports.
I use v13 VIP repack Cataclysm 4.3.4 build 15535 and is my first experience with repacks/wow server.
Click to expand...
If all else fails, you could just change the port used by worldserver.conf to a different, unused port and see if the connection will be allowed. To do that, just go into worldserver.conf and change the ports used by it, and you might have to change the port in the realmlist.
I think I remember a situation where I opened 8085/6 and it told me the port was closed, yet people could still connect - I doubt that'll help your situation, just a note on the reliability of checking if ports are open/etc.
11-04-2025, 05:12 PM
Original source
Well...finally solved it....
what worked for me is:
port 8085 had issues, had to change to 8086.
Changed in worldserver.conf and authserver.conf IPs 0.0.0.0 to the local (LAN) IP of the computer. Apparently 0.0.0.0 works only for local connections, but not remote connections
Changed in worldserver.conf port 8085 to 8086
In DB v13_..._auth > realmlist > data > changed
- IP to my external FQDN
- portnumber from 8085 to 8086
- 0.0.0.0 to the local (LAN) IP of the computer
- subnetmask from 255.255.255.255 back to 255.255.255.0. Apparently the subnetmask is for the network, not for the host.
In port forwarding, forwarding ports 3724 and 8086
Then using powershell's "Test-Netconnection FQDN -port 8086" gave a TRUE
All the same above for port 8085 DIDNT work for me.
Sidenote: this is my first server, I don't have any experience with other servers.
I tried the same with WotLK server, but same result. Hence I knew where to begin troubleshooting. (networking issues)
rektbyfaith
11-04-2025, 05:12 PM #12Archived author: mata1 • Posted: 2025-11-04T18:12:46.019093
Original source
Well...finally solved it....
what worked for me is:
port 8085 had issues, had to change to 8086.
Changed in worldserver.conf and authserver.conf IPs 0.0.0.0 to the local (LAN) IP of the computer. Apparently 0.0.0.0 works only for local connections, but not remote connections
Changed in worldserver.conf port 8085 to 8086
In DB v13_..._auth > realmlist > data > changed
- IP to my external FQDN
- portnumber from 8085 to 8086
- 0.0.0.0 to the local (LAN) IP of the computer
- subnetmask from 255.255.255.255 back to 255.255.255.0. Apparently the subnetmask is for the network, not for the host.
In port forwarding, forwarding ports 3724 and 8086
Then using powershell's "Test-Netconnection FQDN -port 8086" gave a TRUE
All the same above for port 8085 DIDNT work for me.
Sidenote: this is my first server, I don't have any experience with other servers.
I tried the same with WotLK server, but same result. Hence I knew where to begin troubleshooting. (networking issues)
11-04-2025, 05:12 PM
Original source
Quote:3b799e5388 said:Glad you got it figured out, at least. It's been at least 3 to 5 years since I've hosted a private server for public use, and even then I rarely did it, so I don't have a lot of experience in that field, so I couldn't really help much other than the basics.
Well...finally solved it....
what worked for me is:
port 8085 had issues, had to change to 8086.
Changed in worldserver.conf and authserver.conf IPs 0.0.0.0 to the local (LAN) IP of the computer. Apparently 0.0.0.0 works only for local connections, but not remote connections
Changed in worldserver.conf port 8085 to 8086
In DB v13_..._auth > realmlist > data > changedIn windows firewall, allowed INBOUND programs authserver.exe and worldserver.exe
- IP to my external FQDN
- portnumber from 8085 to 8086
- 0.0.0.0 to the local (LAN) IP of the computer
- subnetmask from 255.255.255.255 back to 255.255.255.0. Apparently the subnetmask is for the network, not for the host.
In port forwarding, forwarding ports 3724 and 8086
Then using powershell's "Test-Netconnection FQDN -port 8086" gave a TRUE
All the same above for port 8085 DIDNT work for me.
Sidenote: this is my first server, I don't have any experience with other servers.
I tried the same with WotLK server, but same result. Hence I knew where to begin troubleshooting. (networking issues)
Click to expand...
Thanks for posting what fixed it for you, as this could help others that come across the same issue.
rektbyfaith
11-04-2025, 05:12 PM #13Archived author: mata1 • Posted: 2025-11-04T18:12:46.019093
Original source
Quote:3b799e5388 said:Glad you got it figured out, at least. It's been at least 3 to 5 years since I've hosted a private server for public use, and even then I rarely did it, so I don't have a lot of experience in that field, so I couldn't really help much other than the basics.
Well...finally solved it....
what worked for me is:
port 8085 had issues, had to change to 8086.
Changed in worldserver.conf and authserver.conf IPs 0.0.0.0 to the local (LAN) IP of the computer. Apparently 0.0.0.0 works only for local connections, but not remote connections
Changed in worldserver.conf port 8085 to 8086
In DB v13_..._auth > realmlist > data > changedIn windows firewall, allowed INBOUND programs authserver.exe and worldserver.exe
- IP to my external FQDN
- portnumber from 8085 to 8086
- 0.0.0.0 to the local (LAN) IP of the computer
- subnetmask from 255.255.255.255 back to 255.255.255.0. Apparently the subnetmask is for the network, not for the host.
In port forwarding, forwarding ports 3724 and 8086
Then using powershell's "Test-Netconnection FQDN -port 8086" gave a TRUE
All the same above for port 8085 DIDNT work for me.
Sidenote: this is my first server, I don't have any experience with other servers.
I tried the same with WotLK server, but same result. Hence I knew where to begin troubleshooting. (networking issues)
Click to expand...
Thanks for posting what fixed it for you, as this could help others that come across the same issue.
11-04-2025, 05:12 PM
Original source
There seems to be in issue with people running the battlenet launcher not being able to connect to v13 with the client. Any ideas on a work around?
rektbyfaith
11-04-2025, 05:12 PM #14Archived author: mata1 • Posted: 2025-11-04T18:12:46.019093
Original source
There seems to be in issue with people running the battlenet launcher not being able to connect to v13 with the client. Any ideas on a work around?
11-04-2025, 05:12 PM
Original source
I suggest to let the clients simply run wow.exe, instead of using the battle net launcher.
I use a prepared*, prepackaged 7zip file of the client which I distribute.
I let them unpack the file to a folder of their choosing and run wow.exe.
*wow.mfil has contents replaced and made readonly, otherwise the game overwrites contents
realmlist.wtf contains the correct server address
Is the battle net launcher at all compatible with v13 vip cataclysm 4.3.4?
rektbyfaith
11-04-2025, 05:12 PM #15Archived author: mata1 • Posted: 2025-11-04T18:12:46.019093
Original source
I suggest to let the clients simply run wow.exe, instead of using the battle net launcher.
I use a prepared*, prepackaged 7zip file of the client which I distribute.
I let them unpack the file to a folder of their choosing and run wow.exe.
*wow.mfil has contents replaced and made readonly, otherwise the game overwrites contents
realmlist.wtf contains the correct server address
Is the battle net launcher at all compatible with v13 vip cataclysm 4.3.4?
Recently Browsing
1 Guest(s)
1 Guest(s)
Recently Browsing
1 Guest(s)
1 Guest(s)