candyman200
MIS
I've got several laptop users that travel to remote offices. When there, they might connect via wire or wireless. Checking DNS I've noticed their laptop have 2 leases - one for each NIC. Since all DNS's are in the same domain, at times apps such as Dameware and WhatsUp "get confused" with the multiple IPs.
For example - Loc#1 x.x.90.100 & x.x.90.112, Loc#2 (active) x.x.98.120. In cmd and I ping by name - no resolution, when I ping by each IP, all 3 resolve to the name but even though the PC is active, the ping fails.
Since the user is up-and-running this isn't a critical issue but for a SysAdmin it's confusing to say the least.
To date I've only seen this on one PC but I'm sure there's something out there I'm missing.
My thought is that maybe we should impliment a special scope for wireless users with a short expiration (8-10 hrs or so).
I'd appreciate any comments or suggestions.
For example - Loc#1 x.x.90.100 & x.x.90.112, Loc#2 (active) x.x.98.120. In cmd and I ping by name - no resolution, when I ping by each IP, all 3 resolve to the name but even though the PC is active, the ping fails.
Since the user is up-and-running this isn't a critical issue but for a SysAdmin it's confusing to say the least.
To date I've only seen this on one PC but I'm sure there's something out there I'm missing.
My thought is that maybe we should impliment a special scope for wireless users with a short expiration (8-10 hrs or so).
I'd appreciate any comments or suggestions.