Client Resolution

  • Thread starter Thread starter chris
  • Start date Start date
C

chris

I manage a large # of laptops on a corporate LAN. The
laptops are frequently off the network (out of the
office) and connecting back to the network through a dial-
up/broadband connection. As the laptops return to the
office and are plugged into the network I have problems
resolving them by name. I can ping them, but when I try
to map to them by name I either receive a "network
connection not found" or I am connected to a different
computer.

Any way to resolve this issue?
 
Dealing with laptops is a tough one due to the many variables, one of which
you're currently experiencing.

Are you trying to connect by FQDN or the NetBIOS name?

One way to help is to use a shorter DHCP lease time so the DHCP server will
give up the laptop's IP quicker. One such recommendation is to chop it down
to one day. But, this can cause issues too. If using WINS (connecting by
NetBIOS names), the default lease time (TTL) with WINS is 6 days. You would
have to chop that down too. But (so many 'buts') that can cause an issue
with WINS with the reg/dereg process and will/may generate Event log errors
due to this, I can't remember the Event ID #, but one of my clients has to
deal with the same issue. We chopped the times down to a day and WINS just
barked. Changed the DHCP lease to 4 days and WINS TTL to 4 days and the
errors subsided (pretty much disappeared).

With DNS names, when a client registers, it's TTL is based on the record.
You can enable scavenging to clean up the old records, but in this case you
would need to chop down the TTL and the scavenging time.

This is something you'll have to test out to see what's best for you.
Laptops always throw a wrench into the works.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top