We've had a few end user complaints recently where the user is trying to remote desktop their laptop from a remote location in the office (like a lab or some other cube) and the remote desktop connection won't work because the DNS server thinks their computer is at one IP address, but maybe their laptop is on wireless at the moment and DNS won't resolve their computer name to the wireless IP. If their LAN IP is registered on the DNS server as 192.168.1.50 (for example), and their wireless IP is 192.168.1.242, Windows DNS only seems to "know" one of the IP addresses...usually the LAN. So in the above scenario, they can remote desktop the wireless IP address (not the computer name) and remote desktop will work. Of course, who really knows what the numeric wireless IP address is when it's dynamic. I hope I've explained the issue properly, and I don't understand Windows server/Windows DNS enough to know how to fix this so the users can always use remote desktop to their computer name, regardless of how the laptop is connected to the LAN. Any ideas?