Named Pipes relies on NetBIOS name resolution to function - so the LMHosts entry is probably what fixed it.
However, Win2k will try to do DNS resolution for NetBIOS names (a bit of a PITA in these cases), and that wildcard DNS entry would break it. Not to mention, its pretty much not RFC compliant, IIRC. ------------------------------------------------------ Roger D. Seielstad - MCSE Sr. Systems Administrator Inovis - Formerly Harbinger and Extricity Atlanta, GA > -----Original Message----- > From: Duane Boudreau [mailto:[EMAIL PROTECTED]] > Sent: Monday, October 07, 2002 3:26 PM > To: NT 2000 Discussions > Subject: DHCP/DNS Problem? > > > Hi All, > > A client whose web site I host called this morning with an > internal name > resolution problem, affecting pinging and much more > importantly sql named > pipe odbc connections, effectively breaking their entire > internal network. > > Setup: > I host DNS for client domain, with *.xyz.com and xyz.com > pointing to an > external IP on my server (note the *) > Client found setting on DHCP server where by .xyz.com could > be appended to > requests. > Gateway/Router setup to resolve external request first. > > Solution: > Disabled DHCP and added lmhost files to each server with correct name > resolution and everything is working correctly again. > > My question is: By adding the wildcard catch all to DNS > could/did I break > the internal network? I cant see how, but the client seems to think my > adding the wildcard catch all was responsible. > > Thanks, > Duane > > > ------ > You are subscribed as [EMAIL PROTECTED] > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe send a blank email to %%email.unsub%% > ------ You are subscribed as [email protected] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED]
