TCP/IP BIND error 10013 (server port 80) Permission Denied.

Major BBS or Worldgroup - get and give support here.

Moderator: Mod Squad

Post Reply
tonicfan
Posts: 38
Joined: Wed Apr 18, 2007 5:52 pm

TCP/IP BIND error 10013 (server port 80) Permission Denied.

Post by tonicfan »

I reset my computer tonight and started worldgroup and i got this error.
I was messing around with the microsoft net frame work but i put everything back as it was before and im still getting this error. I checked my router firewall and port 80 is open. I am also not running windows firewall. So i dont know what to do the wgserver wont load! Can anyone help me fix this? I hate having the BBS down due to this weird error :(

This is what the error log says:
C:\WGSERV\wgserver.exe - TCP/IP BIND error 10013 (server port 80) Permission Denied.

In the actual Server in red stated this:
TCP/IP BIND error 10013 (server port 80) Permission Denied.
U#0033,MSG:galwebd.mcv/3
Looks like it showed this when it was loading GALFMEML


Thanks

Stoneslinger76
Posts: 427
Joined: Wed Apr 23, 2008 12:01 pm
Location: Kitchener, ON, Canada
Contact:

Re: TCP/IP BIND error 10013 (server port 80) Permission Deni

Post by Stoneslinger76 »

tonicfan wrote:I reset my computer tonight and started worldgroup and i got this error.
I was messing around with the microsoft net frame work but i put everything back as it was before and im still getting this error. I checked my router firewall and port 80 is open. I am also not running windows firewall. So i dont know what to do the wgserver wont load! Can anyone help me fix this? I hate having the BBS down due to this weird error :(

This is what the error log says:
C:\WGSERV\wgserver.exe - TCP/IP BIND error 10013 (server port 80) Permission Denied.

In the actual Server in red stated this:
TCP/IP BIND error 10013 (server port 80) Permission Denied.
U#0033,MSG:galwebd.mcv/3
Looks like it showed this when it was loading GALFMEML


Thanks
Sounds like ISS (windows web host) services became active. Go to ISS web services configuration and set it to run on port 8080. Then set it so it does not start automaticly and shut it down. Next go to "services" check ISS is not running while their be sure to set it "manual" start mode (not automatic) so it doesnt start when you reboot, you can leave ISS admin running if you want to.

WG should start up now.
Stoneslinger
telnet://theswampbbs.net or http://theswampbbs.net

tonicfan
Posts: 38
Joined: Wed Apr 18, 2007 5:52 pm

Solved! - Kind of.

Post by tonicfan »

The IIS wasnt installed, something must have happened when I installed a net framework and it got disabled in the add/remove components section. How strange. Well I learned something here. I was able to still get the telnet to keep operating though, it was the web service and such that was not working cuz i changed the port so at least someone could still login. I had to login through the direct ip there for a day. Very very strange. But its working once again. In fact i still need to telnet into via the IP and not the tohs.dyndns.org. Outside people can get in but i cannot use telnet://tohs.dyndns.org the connection times out. So there is still that issue i guess, im not sure why its doing that.

User avatar
dspain
Posts: 2102
Joined: Sun May 07, 2006 10:38 pm
Location: richmond,virginia
Contact:

Re: Solved! - Kind of.

Post by dspain »

tonicfan wrote:The IIS wasnt installed, something must have happened when I installed a net framework and it got disabled in the add/remove components section. How strange. Well I learned something here. I was able to still get the telnet to keep operating though, it was the web service and such that was not working cuz i changed the port so at least someone could still login. I had to login through the direct ip there for a day. Very very strange. But its working once again. In fact i still need to telnet into via the IP and not the tohs.dyndns.org. Outside people can get in but i cannot use telnet://tohs.dyndns.org the connection times out. So there is still that issue i guess, im not sure why its doing that.
port 80 is being used by another application, some routers with remote access enabled default to port 80 as well.

checks for IIs, apache, or any other web appl that can using port 80 for communication

Post Reply