Troubleshooting unavailable website

[Monte Grant]

A sharepoint teamservices site is the default site on an xp pro machine
w/anonymous access on port 80.

The domain is redirected to the router's IP by an online service. The
router forwards the http request to port 80 of the xp machine.

This has worked smoothly for 2 years, until I installed xp sp2.


Now I can access the site from the xp machine by typing http://localhost, or
by entering the local network private IP address on another networked
(behind the router) machine.


There is a 2nd machine with an identical setup, except that it is a w2k
machine and that the router forwards to port 8081 for its Virtual Server.
It currently works properly and has an identical setup at the web redirect
service.



If I try to get to the website via the internet, I get "Page cannot be
found" "Cannot find server or dns error."

How can I troubleshoot this problem?

Nick

 

[Jason Brown [MSFT]]

Sounds to me like you just need to add an exception in the XP SP2 firewall
settings. I take it you haven't already done this?


--
Jason Brown
Microsoft GTSC, IIS

This posting is provided "AS IS" with no warranties, and confers no
rights.

 

[Monte Grant]

Thanks for your help with this. The Windows firewall has been disabled
since sp2 install. We are behind a router.

Nick

 

[Jason Brown [MSFT]]

So the windows firewall is off. OK, have any changes been made to :

the router (assuming it's firewalled or port-forwarded)
the NTFS permissions on the web files

also is the name still resolving to the correct IP address?


--
Jason Brown
Microsoft GTSC, IIS

This posting is provided "AS IS" with no warranties, and confers no
rights.

 

[Monte Grant]

Router is still forwarding port 80 http requests to the correct IP.

I have not messed with permissions but looking at wwwroot and all contents,
the internet guest account appears to have read access.

As for resolving to the correct IP, the redirect service lists the IP
address of the router. I did notice that if I enter http://routerIP, I
cannot connect and get the same error as if I typed the website name. I can
only connect through my local internet to the site by entering either
localhost or the machine's private IP.

Nick

 

[Monte Grant]

Running ipconfig, the wireless adapter's "Connection-specific dns suffix" is
listed as "attbi.com"

This seems odd as I now have an account with comcast.net.

 

[Jason Brown [MSFT]]

So in view of that I'd suggest perhaps the router has stopped forwarding
correctly, for whatever reason. is the machine inside the router still on
the same IP address that the router is trying to forward to?


--
Jason Brown
Microsoft GTSC, IIS

This posting is provided "AS IS" with no warranties, and confers no
rights.

 

[Monte Grant]

Yes the router settings indicate that it continues to forward to
192.168.0.100 port 80 public and private, though I do not know how one can
verify this. Maybe it is not functioning properly though it says it is.
IIS default web port is set to 80.

Nick

 

[Jeff Cochran]

Yes the router settings indicate that it continues to forward to
192.168.0.100 port 80 public and private, though I do not know how one can
verify this. Maybe it is not functioning properly though it says it is.
IIS default web port is set to 80.

Can you telnet to port 80 on the system? Is there a firewall you may
be missing that now blocks port 80? At your ISP perhaps?

Jeff