Ts / Vm / Iis - 404 / 403

Environment:
[INDENT]TeamSite 6.5 SP1
W2K3 via VMware (I believe*)
IIS v6
(*I am not directly responsible for this server, I believe this is a W2K3 virtual instance running off of a linux box - this is a development server)[/INDENT]

Problem
[INDENT]As one might expect - the problem is that virtualization isn't working - when we try to visit a page on a remote system via the TS GUI - the URL appears as (example IP used here):
http://123.45.6.7/iw-mount/default/.../foo.html
and we get a 404 error message.
[INDENT]Note: 123.45.6.7 is the IP of the hosting server. If I want to bring up a Remote Desktop on the TS server - it would be 123.45.6.7:3306; It's unclear to me what the correct IP address should be for accessing files remotely from a virtual server (the hosting server's IP, the virtual server's IP, something else??)[/INDENT]
I get the same error if, on the TS server, I bring up Computer Management, go through the IIS instance and navigate through iw-mount to the same page and then right-click and do Browse
If I try to Browse the iisstart.htm page at the top-level of the IIS web server (through Computer Management) - I get a 403 error.[/INDENT]

I've never claimed to be IIS proficient (I'd be happy if I never had to touch it at all) - so I'm hoping someone here might be able to guide me towards a resolution of this issue.
[INDENT]Note: My understanding is that "things were working a day or two ago" - but since nobody seems to know what happened / what they did to make it stop working - that doesn't really help me too much - sigh[/INDENT]

Feel free to ask for additional information that will help you help me to resolve this issue - best if you tell me also how to obtain that information too (I'm much more Unix literate than Windows literate) - and I'll try to provide it.

Thanks

Find more posts tagged with

Comments

stefanmaier

Hi Fish,

only a shot in the dark...
You say, that 123.45.6.7 is the IP address from the HOST server.
But isn't it so, that you want to request your IIS on your VIRTUAL server (the server where TS is installed)?
Fist let's check, what's the correct IP adress from your virtual server with an "ipconfig"...

Also you should check, if the "iw-mount" webapplication is configured correctly.
I remember, that we had some problems with the TS installer: open the "Properties"-sheet from the iw-mount webapp,
Then check "local path", there should be a "Y:\".

Regards
Stefan

Adam Stoller

Hi Fish,

only a shot in the dark...
You say, that 123.45.6.7 is the IP address from the HOST server.
But isn't it so, that you want to request your IIS on your VIRTUAL server (the server where TS is installed)?
Fist let's check, what's the correct IP adress from your virtual server with an "ipconfig"...

Perhaps I wasn't clear (or perhaps I was?):

On TS server: ipconfig will return something like 231.53.6.78

From remote computer - to connect to TS server with remote desktop - I need to use an IP like: 123.45.6.7:3606 (where '123.45.6.7' is, I believe, the linux box's IP and '3606' is, I believe, the port for the virtual W2K3 server on the linux box)

From remote computer - through TS GUI - if I try to preview a page the URL that shows up in my browser is http://123.45.6.7/iw-mount/... (no port specification) - I can't use the IP of the VM W2K3 server because that's not a public IP. I tried putting the '3606' port in there too but that doesn't work either.

Also you should check, if the "iw-mount" webapplication is configured correctly.
I remember, that we had some problems with the TS installer: open the "Properties"-sheet from the iw-mount webapp,
Then check "local path", there should be a "Y:\".

That part is fine - (otherwise I wouldn't have been able to navigate through there - but I checked the Properties anyway)

stefanmaier

Do you have the possibility to have a look into the VMware network options?

nipper

Can you get to ANY of the vmware networking pages ?

i.e. http://231.45.67.8:81/ for the main IIS page.

Can you run VMWARE and look at the screen of the Win2K implementation itself and open a browser inside it. It certainly seems to have the routing screwed up for that box.

Andy

Adam Stoller

Can you get to ANY of the vmware networking pages ?

i.e. http://231.45.67.8:81/ for the main IIS page.

From the Remote Desktop connection to the W2K3 VM instance - if I bring up a browser and try to go to the internal ip address as indicated - I get an HTTP 401 (unauthorized) error message.

This sounds somewhat promissing however I'm still not sure what the issue is or how to resolve it.

Can you run VMWARE and look at the screen of the Win2K implementation itself and open a browser inside it. It certainly seems to have the routing screwed up for that box.

I don't have [direct] access to the hosting server - I could suggest this to the IT person but it would help to have some idea to tell them what to look for...

Do you have the possibility to have a look into the VMware network options?

Is there something in particular that should be looked for / looked at?

(sorry if these questions seem stupid - but I really have no clue about using / configuring VMware or IIS - and, in general, I'd like to keep it that way Smiley Happy

)

stefanmaier

Is there something in particular that should be looked for / looked at?

There're different possibilities to configure a VM network:
1. bridged mode: the virtual server has an official IP address, so that you can use this address in your client browser
(not in your case, 'cause you say there's no official IP)

2. NAT mode: this mode is used to share the hosts IP address (host and virtual machine have the same IP adress)

3. private network: host and vm server have different IP addresses (could be your scenario),
but: virtual machine is only accessable by host 'cause virtual servers IP adress is not offical.
(it's like an additional network interface whereby only the virtual server ist connected)
Sometimes this mode is extened by a proxy-like software installed on the host machine to connect to
vm (then it's a little bit like port forwarding...)

So, perhaps we can get closer to your problem, if we know something more about the network connection.

nipper

Do you have access to the Linux server ? That needs to do routing to the VMware instance. Can you ping, etc from it to vmware ?

Adam Stoller

Do you have access to the Linux server ? That needs to do routing to the VMware instance. Can you ping, etc from it to vmware ?

I don't - but I've passed on the previous questions to the IT person in the hopes that he can provide the information (I believe the system was set up by someone else who's no longer working there - so it could be an historical problem)