rice chrisp
27-12-2005, 23:50
I'm posting this in General in hopes that it will get more views than it's getting in Server Support (My apologies for posting this twice, it's just kinda frustrating is all...)
Long time client, first time server user here. I've been struggling to get my server up and running for my guild (in WoW) since yesterday afternoon and sifting through the various manuals and FAQs here and I thought I was making progress until I saw this:
---------------------------------------------------------------
-------------- log started at 27-12-05 15:47 -------------
---------------------------------------------------------------
27-12-05 15:47:14,ALL,Info,server, Server init initialized
27-12-05 15:47:14,ALL,Info,server, Server version: 2.0.20.1 Win32
27-12-05 15:47:15,ALL,Info,server, Starting VirtualServer id:1 with port:8767
27-12-05 15:47:15,ERROR,All,SERVER, VirtualServer startup failed with port 8767, Exception: EIdSocketError.Socket Error # 10049
Cannot assign requested address.
27-12-05 15:47:15,ERROR,All,WEBINTERFACE, WebInterface startup failed with port 14534, Exception:Socket Error # 10049
Cannot assign requested address.
27-12-05 15:47:15,ERROR,All,TCPQUERY, TCPQuery startup failed with port 51234, Exception: Socket Error # 10049
Cannot assign requested address.
27-12-05 15:47:15,ALL,Info,server, Server init finished
I started receiving this error after I edited my server.ini file, this line specifically:
BoundToIp1=67.139.91.84
I have 2 IPs under the "Your IPs" menu.
192.168.1.101 (which obviously is my private IP)
and
67.139.91.84 (the IP I give out to my guildies of course)
The reason I changed the BoundToIp line was because leaving it blank didn't seem to help, i.e. I could log on but none of my guildies could when I gave them the WAN IP. However, changing it (as has been suggested in the FAQs and a bunch of threads in these forums) only seems to have made things worse!
Any help you experts could offer would be greatly appreciated, thanks
P.S. I have a NetworkEverywhere Linksys router, model # NR041 and already went in and tweaked the port triggers to get 8767 opened up.
One more thing...
I just changed my server.ini file back to "BoundToIp=" setting it equal to nothing, as is the default value. It seems the server is starting up fine now and when I log in on the computer I have my server running on with my private IP (192.168.1.101) as the server address everything runs smoothly. The strange part is when I attmept to log in with the WAN IP (67.139.91.84) I connect to the server succesfully and then almost immediately my connection times out.
Sorry for the long post, I'm trying to be as thorough as possible to accomodate you TS geniuses out there :)
Long time client, first time server user here. I've been struggling to get my server up and running for my guild (in WoW) since yesterday afternoon and sifting through the various manuals and FAQs here and I thought I was making progress until I saw this:
---------------------------------------------------------------
-------------- log started at 27-12-05 15:47 -------------
---------------------------------------------------------------
27-12-05 15:47:14,ALL,Info,server, Server init initialized
27-12-05 15:47:14,ALL,Info,server, Server version: 2.0.20.1 Win32
27-12-05 15:47:15,ALL,Info,server, Starting VirtualServer id:1 with port:8767
27-12-05 15:47:15,ERROR,All,SERVER, VirtualServer startup failed with port 8767, Exception: EIdSocketError.Socket Error # 10049
Cannot assign requested address.
27-12-05 15:47:15,ERROR,All,WEBINTERFACE, WebInterface startup failed with port 14534, Exception:Socket Error # 10049
Cannot assign requested address.
27-12-05 15:47:15,ERROR,All,TCPQUERY, TCPQuery startup failed with port 51234, Exception: Socket Error # 10049
Cannot assign requested address.
27-12-05 15:47:15,ALL,Info,server, Server init finished
I started receiving this error after I edited my server.ini file, this line specifically:
BoundToIp1=67.139.91.84
I have 2 IPs under the "Your IPs" menu.
192.168.1.101 (which obviously is my private IP)
and
67.139.91.84 (the IP I give out to my guildies of course)
The reason I changed the BoundToIp line was because leaving it blank didn't seem to help, i.e. I could log on but none of my guildies could when I gave them the WAN IP. However, changing it (as has been suggested in the FAQs and a bunch of threads in these forums) only seems to have made things worse!
Any help you experts could offer would be greatly appreciated, thanks
P.S. I have a NetworkEverywhere Linksys router, model # NR041 and already went in and tweaked the port triggers to get 8767 opened up.
One more thing...
I just changed my server.ini file back to "BoundToIp=" setting it equal to nothing, as is the default value. It seems the server is starting up fine now and when I log in on the computer I have my server running on with my private IP (192.168.1.101) as the server address everything runs smoothly. The strange part is when I attmept to log in with the WAN IP (67.139.91.84) I connect to the server succesfully and then almost immediately my connection times out.
Sorry for the long post, I'm trying to be as thorough as possible to accomodate you TS geniuses out there :)