Chatter Of The Squirrel

Windows Server 2003 x64 Weirdness

January 19, 2007 on 1:58 pm | In Me! | No Comments

Running the new Windows Server 2003 at work… the 64-bit version no less…

Using it to develop web apps, and learn ASP etc.

Had this weird problem when I use IIS 6.0…

The “Default Website” won’t run. Unless I change it from port 80 to something else…

Which is kinda silly. What’s stopping the IIS from using port 80?

That’s like having a convertible that doesn’t run when the top is down. What’s the point of a convertible if you can’t feel the wind in your hair?

Thought it was some virus or something that’s using the TCP port. When I manually start the Default Website on IIS, I get the following error: “The process cannot access the file because it is being used by another process.”

So…

C:Documents and SettingsAdministrator>netstat -ano

Active Connections

  Proto  Local Address          Foreign Address        State           PID
  TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       1004
  TCP    0.0.0.0:81             0.0.0.0:0              LISTENING       1656
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING       828
  TCP    0.0.0.0:443            0.0.0.0:0              LISTENING       1004

Then…

C:Documents and SettingsAdministrator>net stop http

The HTTP service was stopped successfully.

C:Documents and SettingsAdministrator>netstat -ano

Active Connections

  Proto  Local Address          Foreign Address        State           PID
  TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       1004
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING       828
  TCP    0.0.0.0:443            0.0.0.0:0              LISTENING       1004
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING       4
  TCP    0.0.0.0:1025           0.0.0.0:0              LISTENING       476 

Something is still occupying port 80.

Using Task Manager, I finally found out that PID 1004 is Skype!

Opening Skype -> Options -> Connections, I find this little check box for “Use port 80 and 443 as alternatives for incoming connections.”

Unchecking the box, restarting Skype, and restarting Default Website fixes the problem.

Home users won’t notice anything when Skype is using up port 80… but it matters a lot to a server machine that’s using IIS.

Pretty basic stuff… But it still puzzled me for a bit before I figured it out.