0

A follow-up to XP Clients lose WINS registrations

I have now run wireshark on an XP workstation as the problem occurs. A request for "foo" goes to the AD server which responds with "Requested name does not exist" yet on the AD server itself it can resolve "foo" just fine.

Unsure what to do next. It's clearly a problem on the Win2k3 SBS box but I'm not a Windows admin guy :-(

Community
  • 1
James Green
  • 11
  • 1
  • you have two different resolvers one is DNS and one is WINS. Clients react differently based on there client level. Are you all xp clients or do you have a mix xp/win7/vista maybe mac's etc? – tony roth Dec 07 '10 at 16:38
  • XP for workstations. We have got Linux development servers too. – James Green Dec 07 '10 at 16:47
  • on the xp workstation do a ipconfig /all, does the dns suffix search list seem correct? – tony roth Dec 07 '10 at 17:23
  • Yep although we rarely use it. For us we say "foo" rather than "foo.company.local" as "foo" is statically mapped for us. "foo" by itself usually works fine and still does on the AD when the workstation receives a "Requested name does not exist" from the AD. – James Green Dec 07 '10 at 17:37
  • so can you do nslookup "foo" from a workstation? – tony roth Dec 07 '10 at 17:55
  • also as an fyi, we don't call it the AD we call it the DC for domain controller. – tony roth Dec 07 '10 at 17:59
  • tony - yes I can do an nslookup foo and get results. But then if I ping (during an "outage") it fails to resolve. – James Green Dec 08 '10 at 11:15

1 Answers1

0

A few Qs:

  • Are you referring to the name as \\foo, foo, or foo.yourdomain.com? Try it on the client and server, and post the results for each test.
  • Are your DNS server(s) configured to refer to WINS?
  • Is your DC running the WINS role; are you seeing UDP port 137 in your wireshark trace?

Cheers.

Simon Catlin
  • 5,222
  • 3
  • 16
  • 20
  • Simon: 'foo', not foo.company.local or \\foo. foo.company.local does continue to work even though foo on it's own does not on the workstation (until I re-register dns). I can't see why the DNS servers would need to refer to WINS? The workstations are clearly working most of the time, wireshark shows UDP/137 traffic with the WINS server / AD server telling it that foo does not exist until the workstation issues an ipconfig /registerdns. – James Green Dec 08 '10 at 11:13