1834456 Members
3180 Online
110067 Solutions
New Discussion

Re: DNS and XP

 
Fred Martin_1
Valued Contributor

DNS and XP

If you have any experience with Windows XP and DNS issues, please see my other post:

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xc4fd77d813646948a29192c1dfe49df3,00.html

Got users with XP laptops, and DNS gets fouled up when they move from a dial-up on the road, to a NIC in the office.
fmartin@applicatorssales.com
3 REPLIES 3
Steven E. Protter
Exalted Contributor

Re: DNS and XP

As I recall from XP(my XP box is at home and I hate it), you can set up these users with two DNS servers on the NIC card.

Find the LAN connection wherever XP hides it and make sure those settings are hardcoded correctly for your local environment.

In dial up networking, you should usually let the ISP set the DNS servers at dial in. There is a check box for that.

If they are hooking into a hotel fast ethernet connection, that makes it a little more annoying, because its probably using the same NIC card as local.

For most hotels all the setting MUST be assigned by the local server whent he NIC card boots.

This might not work so well with your NIC environment.

If you can get everything so its set in your lcoal environmetn at boot/connect time, the problem should not happen.

I'd look at ipconfig output when those users come home. There is probably something wrong there.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Ron Kinner
Honored Contributor

Re: DNS and XP

Need a bit more info. Are you using DHCP in the office? If so what is it running on? Is there a WINS server? Do you have control of the DNS? What version is it (bind?) and what does it run on? If you delete the secondary DNS on the XP does the problem still occur?

Ron
Ron Kinner
Honored Contributor

Re: DNS and XP

Run
netsh interface dump > junk1

junk1 will contain the current config info on the network. Next time it acts up run the same command except use junk2 then compare the two files. That should show you what is going on. You can use netsh to make changes to fix the problem and incorporate the changes into a login script.

Ron