Problem accessing Port 80 on Terminal Services

[webuser]

Here is my situation. I have several clients, all at different locations who are having a problem accessing a Terminal Services Web Page (i.e TSWEB). Here is the catch: the problem only occurs at night, seemingly after midnight. It seems to go away every morning sometime b/w 7:30 AM and 8:00 AM when everything works again perfectly. We are extremely puzzled.

Here is the Network layout: The users access the Termimnal Services web page through a mapped IP address on a Netscreen 5 firewall. The TS machine is running Windows Server 2003. There are only 2 other machines on this network - both Windows 2003 DCs. One is a SQL Server machine. We don't think it is DNS related b/c some of the machines are using Hosts files...

We have checked the logs on the TS machine as well as the DCs and the Netscreen with nothing obvious. We have never used schedules of any kind to restrict access, and can't find any settings that would suggest that anyone put any in place.

Below is the exact error message that users recieve:

"Cannot access the Web Site. Please check your proxy setting. Made http request for GET /tsweb/defaultlogin.asp HTTP/1.1 to pegasus:80. The URL you entered is incorrect or the Web site is not accessible. Administrator: Please ake sure that the DNS Domain information is entered correctly. Made http request for GET /tsweb/defaultlogin.asp HTTP/1.1 to Pegasus:80

Pegasus is the name of the TS machine. We suspect it is something with the firewall, but there is nothing in the logs, so we don't know.

Has anyone heard of anyhting time related like this? Any help would be GREATLY appreciated!!!

Thanks in advance!

 

[technome]

During these outages can the firewall be pinged. Nslookup functional.

Power management in the bios or Windows

auto logoff on machines default to 15 minutes, raise it

Are your switches, broadband modem and firewall on a UPS. Power util companies switch grid in the early a.m hours causing power flucuations.

Does your gateway router have a keep alive setting.

For the hell of it run DCdiag.exe and Netdiag.exe to check AD and DNS health. Does not sound like a DNS error or you would not have access during the day.


Any error logs on the server or remotes

 

[bcastner]

Check the router. Many have time of day access controls.