Question Locked

VPN & Remote desktop problems

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I work for a small company where we have a windows 2000 server domain(not 2003). For a little history, we've had a couple of different IT consultant companies taking care of our network over the last couple of years. When we had our original IT company, who setup the server and domain, everything with VPN and Remote Desktop were working fine. I mention this since each of these consultants have used different remote administration software to work on our servers(some of which have been un-installed), which could be contributing to our problem. We also do not have a full-time onsite IT person, though I have a strong understanding of domain admin, so I get the day to day little fixer problems. So here is the problem:

Server 2000 - This is our VPN server, File server, IIS server, and Exchange server (I know that's a lot, don't get me started). It obviously has both a live IP address for VPN and IIS as well as another adapter with a Private IP address for it's file server duties.

Remote Desktop 'targets' - Multiple desktop machines running Windows XP, all of which are part of the domain. These machines are inside the firewall, and are served out private ip addresses from our DC. We have tried to connect to these computers via IP address and Computer Name, from outside of the domain without success.

Now, again, previously, our VPN, Firewall, etc. were all configured correctly and we were able to remote into these private IP machines from outside of the domain by turning on the VPN connection. Now the only way we can remote into these machines is to Remote into our server, then in that remote session, create a remote session to the private machines. We were really not able to pinpoint what happened that caused this to suddenly stop working for the machines with private IP addresses. The Windows 2000 server that has a live IP is accessible via Remote desktop sessions, but none of the private IP machines.

Any ideas of what may have happened here? Could it be that when some of the old remote administration programs left behind files/registry entries that are causing issues with address resolution?

We want to get back to the point where we can remote into our desktop machines from offsite without having to go through multiple Remote Desktop sessions. Any help pointing me in the right direction for research or a solution would be very helpful.

4 replies

by cg it

For VPN to work on a Windows Active Directory domain, you need to enable Routing and Remote Access [RRAS], setup a pool of addresses for remote access clients to use [on the local subnet], then create rules in RRAS to allow those domain users who have permission for remote access to have remote access [there is a domain security account for remote access users]. You also need to setup remote access in the users Active Directory account [or as mentioned place their user account in the remote access security group].

This setup provides remote users domain authentication and an address on the local network. Users can then access domain resources remotely.

Remote Desktop to a workstation requires you to enable remote desktop on individual workstations and allow a direct connection from the internet to the workstation [and as BFilmfan says, opening up the appropriate ports on the firewall for Remote Desktop.

by rootrat

Well, the solution was simple, but nothing we were thinking. I went through the posts and made sure that the Firewall/RRAS/VPN and such were configured correctly. Then since it still wasn't able to RDP into an internal machine, I checked out ipconfig of the VPN'd machine and noticed that it did not have a DNS server assigned.

So I went into the RAS console and saw the little drop down box on the IP tab: "Use the following adapter to obtain DHCP, DNS, and WINS addresses for dial-up clients."

The server has 3 NIC ports, and only two connections (LAN & WAN). It appears that at some point, a network cable was put back into the wrong NIC slot, so DNS lookup requests were being sent to an adapter that had no physical connection.

Thanks again for pointing me at the right interfaces and places to look for problems.

This discussion is closed to new replies.