>>On an network that uses DHCP, if you open the Remote Desktop client and >>just select a previously-selected computer name from the list, and if >>the IP that your target used the last time has subsequently been given >>to another PC via DHCP, you log onto the *new* PC, not the one you >>intended. Has anyone seen this before?
It's probably a 'feature' of Remote Desktop. I imagine it 'caches' the IP addresses of the names/IPs. If you pick from a previous name in the list it may first try it's cached IP address for speed purposes (e.g. so it didn't have to go out and 'look up' the IP address based on a PC name). I wonder if it retains that 'cache' between sessions. That would definitely seem like a dumb design idea IMO. Did you try (or is it even possible) to completely exit Remote Desktop after connecting the first time?
Probably not a feature of remote desktop at all, but rather a local OS cache. When this happens, try pinging by name and see what it resolves to. You can issue "ipconfig /flushdns" and try it again to see if it's a local DNS caching issue. It's also possible there's a DNS caching server that hasn't updated with the new DHCP-assigned address. Be sure the destination computer has "register connection in DNS" checked in network settings for the local NIC as well... -- Derek _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
