Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We maintain a Windows 2003 Terminal Server for one of our remote offices to connect to to get all their work done. Every morning, when they try to connect, they get an error that the server is unavailable. From our ouwn internal network, we are able to log into that server using RDP just fine. After rebooting the server, the remote office is able to connect once more. It would seem to me (maybe incorrectly though) that given the symptoms the problem isnt with the network (which doesnt change after a reboot) or with all the licenses used up (we are able to log in.) But I have no idea what the problem could be. Any ideas in troubleshooting this will be greatly appreciated.

Additional Information: (5/1/2012)

First, I want to thank everyone who has had suggestions so far. They have been great. So I tested a few things and these were the results: When the connectivity is lost from the outside subnet, I logged into the server locally and attempted to access the subnet. It failed saying "No Network Path Provider was available." Then I did a quick Google search in the browser and after calling up the Google page I was once more able to see the blocked subnet.

We have used the Windows ARP command to check that the MAC addresses of the NIC cards on the server match the ARP cache, and likewise we have checked the Cisco ASA 5500 Router's ARP cache for incorrect entries.

share|improve this question
    
Are the working internal systems on the same subnet as the server? –  Shane Madden Apr 12 '12 at 15:41
    
Hi Shane. Yes they are on the same subnet. –  Goblyn27 Apr 12 '12 at 16:01
    
Next time it happens, check outbound connectivity from the server (through the console or RDP from one of the local systems) - I bet it won't be able to access anything outside the subnet. –  Shane Madden Apr 12 '12 at 16:20
    
Ok, good advice I will try that. –  Goblyn27 Apr 12 '12 at 16:26
2  
It would help if we could see a diagram of the network topology that shows how the server, ASA 5500, and any other devices sitting between your site and the remote subnet are connected to each other. That said, LAN-to-LAN IPsec VPN tunnels on Cisco devices are brought up "on demand", meaning the ASA will only try to bring a tunnel up if it sees a packet that it thinks needs to cross that tunnel. I've seen cases where a tunnel will only come up when triggered from one end, which may be what's going on here. –  James Sneeringer May 3 '12 at 2:18

2 Answers 2

Try performing a series of tracert commands from your local subnet and from the remote subnet during the day. See if the route changes, or can't be resolved.

share|improve this answer
up vote 0 down vote accepted

It turns out that the problem was with the multiple NIC cards on the server. Each NIC was for a different subnet. For some reason, the server would eventually get confused and stop responding to RDP requests on the NIC unless I first logged into the server and made an outbound request. Once I disabled the other NIC, it was golden.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.