IIS+Virtualcenter=huge headaches?

[spotz300tt]

Anyone successfully running IIS on VC on the same server? It looks like VC wants to take port 80 on any IP address it can get its hands on (no matter what you tell it to do).

I am trying to running WSUS and VC on the same server, and prefer not to run WSUS on an odd port assignment, but it doesn't look like VC will start if ANYTHING is running on port 80 on the localhost.

Anyone had any similar issues?

Thanks,

Chris.

[Texiwill]

Hello,

Yes I do this. Actually I define VC to use port 81 and 443 (SSL) while my IIS uses port 80 and 8443 (SSL). I have to do this for some braiddead software I installed for patch management. Frankly I never use port 81 at all, only https.

Best regards,

Edward

[spotz300tt]

What version of VC are you using? I told mine to run on port 8080 and it is still locking up 80... I am running 2.02

[Texiwill]

Hello,

If you use the 'Repair' method you will see all the ports it runs on. I think you have one still set to use 80. VC 2.0.2 will warn you of this case. It did when I upgraded. You need to make sure you select that you WANT to change it. Read the dialog carefully.

Best regards,

Edward

[spotz300tt]

I went back, did an uninstall/re-install made sure I selected port 81 for www traffic and still get the same thing.

From the logs:

\[2007-08-08 13:27:15.984 'App' 5000 error] \[VpxdVmomi] http proxy failed on port 80: Only one usage of each socket address (protocol/network address/port) is normally permitted.

\[2007-08-08 13:27:15.984 'App' 5000 error] \[VpxdVmomi] Failed to start http proxy: Only one usage of each socket address (protocol/network address/port) is normally permitted.

Clearly it is still trying to bond to port 80.

Message was edited by:

spotz300tt

[spotz300tt]

Okay....I got it.

Brute force wins out.

This file controls it:

C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\vpxd.cfg

In there you can see that it has a http section... I never saw it directly call port 80 (there is a space in the registry where it seems like it \*should* be calling it, but mine lists port 81).

My solution... Take out the entire section that mentions http traffic. I don't want it, or need it. Problem solved.

Chris.