Here are the particulars--
Windows 2003 Standard SP1
Multihomed--192.168.105.45 & 10.18.8.45
RDP enabled on computer.
I am on same LAN as this machine and can rdp to it to my heart's content using either IP address.
User on the WAN however can not connect to 192.168.105.45 using rdp. He gets the generic RDP might not be enabled or too busy to accept connections.
Now I know everyone is thinking firewall right now, but get this.
The user only has problems from about 00:00 EST until 0400 EST. Outside of those times he can connect without issue. The user is actually in India. To further muddy the waters this user can connect to other servers on the same subnet as the one he can't connect to. Other users in the same location as this user can connect to all servers but this one.
Windows Firewall is not running on this server. Thought maybe a scheduled task is executing to max out the NIC or something but there aren't any. Nothing on this server is backed up, so there isn't a backup job or something maxing out the NIC either.
I created a scheduled task on another server on the same LAN to launch rdp to connect to the server using a specific user account. A startup bat file for that user then logged off. This ran every 10 minutes for 2-3 days and did not encounter any problems.
Nothing relevant in Event Viewer.
The only thing I have left to do is to run Wireshark on the server to see if the client requests are reaching the server. Can anyone think of a router/firewall problem that could be time-based? I mean whatever is the problem is only lasting a couple of hours.
I don't think it can be anything on the user's computer because others on his LAN are experiencing the same symptoms.
Looking forward to responses.