name resolution by fqdn but not by netbios name JBeckett [MCSA] 5/14/2007 10:01:01 PM I have serveral linux-based file servers that store various software updates that get distributed to my Windows XP clients. When we installed Windows Server 2003 we switched from WINS to DNS, since doing that my XP clients cannot find my linux file servers by the netbios name as they were able to when we were using WINS. If I ping by the fqdn (ex. pgmob1.dvmc.local) I get a response, but if I ping by the netbios name (pgmob1) I get no response. I manually created the A records in DNS for the file servers in the same zone as my XP workstations, however the file servers are not joined to the domain.

RE: name resolution by fqdn but not by netbios name Not So Incredible Hulk 5/14/2007 11:23:00 PM Have you done something to change the primary domain suffix specified on the clients? Is "Append primary and connection specific DNS suffixes" selected on the client TCP/IP DNS Properties? What you are doing should work. "JBeckett [MCSA]" wrote: [Quoted Text] > I have serveral linux-based file servers that store various software updates > that get distributed to my Windows XP clients. When we installed Windows > Server 2003 we switched from WINS to DNS, since doing that my XP clients > cannot find my linux file servers by the netbios name as they were able to > when we were using WINS. If I ping by the fqdn (ex. pgmob1.dvmc.local) I get > a response, but if I ping by the netbios name (pgmob1) I get no response. > > I manually created the A records in DNS for the file servers in the same > zone as my XP workstations, however the file servers are not joined to the > domain.

RE: name resolution by fqdn but not by netbios name JBeckett [MCSA] 5/15/2007 12:05:00 AM Yes...when the original NT4 domain was setup the domain controller was setup with a .com extension which I then changed to .local. All of my clients the option 'Append primary and connection specific DNS suffixes' selected and an IPCONFIG /ALL shows that the client has the .local extension. "Not So Incredible Hulk" wrote: [Quoted Text] > Have you done something to change the primary domain suffix specified on the > clients? Is "Append primary and connection specific DNS suffixes" selected > on the client TCP/IP DNS Properties? > > What you are doing should work. > > > > "JBeckett [MCSA]" wrote: > > > I have serveral linux-based file servers that store various software updates > > that get distributed to my Windows XP clients. When we installed Windows > > Server 2003 we switched from WINS to DNS, since doing that my XP clients > > cannot find my linux file servers by the netbios name as they were able to > > when we were using WINS. If I ping by the fqdn (ex. pgmob1.dvmc.local) I get > > a response, but if I ping by the netbios name (pgmob1) I get no response. > > > > I manually created the A records in DNS for the file servers in the same > > zone as my XP workstations, however the file servers are not joined to the > > domain.

Re: name resolution by fqdn but not by netbios name "Mike Spike" <Mike[ at ]melted-Cpu-co.uk> 5/17/2007 4:07:51 PM You might need to add them into your WINS server in your Windows Server OS. If the computers can not find the Linux computer it will try appending every possible variation of the dns labels / suffixes + Linux single label name and when that fails it will still try Netbios / Wins before giving up. regards, Mike. "JBeckett [MCSA]" <JBeckettMCSA[ at ]discussions.microsoft.com> wrote in message news:BFA8DDBE-506F-4BF1-A2BB-806B36254A9B[ at ]microsoft.com... [Quoted Text] >I have serveral linux-based file servers that store various software >updates > that get distributed to my Windows XP clients. When we installed Windows > Server 2003 we switched from WINS to DNS, since doing that my XP clients > cannot find my linux file servers by the netbios name as they were able to > when we were using WINS. If I ping by the fqdn (ex. pgmob1.dvmc.local) I > get > a response, but if I ping by the netbios name (pgmob1) I get no response. > > I manually created the A records in DNS for the file servers in the same > zone as my XP workstations, however the file servers are not joined to the > domain.

Re: name resolution by fqdn but not by netbios name JBeckett [MCSA] 5/17/2007 4:16:01 PM We were trying to weene ourselves off of WINS but it looks like I'm not going to be able to get away from it. Thanks for the tip!

Re: name resolution by fqdn but not by netbios name "Mike Spike" <Mike[ at ]melted-Cpu-co.uk> 5/17/2007 4:56:11 PM Sorry I did not read your first post properly: <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< I manually created the A records in DNS for the file servers in the same zone as my XP workstations [Quoted Text] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>... I missed that bit. In that case there is no reason why the servers should not resolve, they don't have to be registered in Active directory. I have done something like this with Linux based anti-spam boxes on a Windows 2000 AD based network. All I did was add an A record just like you: Anti-Spam1.Domain.local, Anti-Spam2.Domain.local I sometimes do this for printers and print servers so I can remember where the WebManagent pages are. I can then type http://Anti-spam1/ into a browser and the Web control panels load up. So I don't why your names are not resovling, but I do know what you are trying to do is possible. Someone mentioned the default suffix of your domain, this sounds like a good place to start. Mike. "JBeckett [MCSA]" <JBeckettMCSA[ at ]discussions.microsoft.com> wrote in message news:39D6626F-081B-4A75-B9CE-770343E1054E[ at ]microsoft.com... > We were trying to weene ourselves off of WINS but it looks like I'm not > going > to be able to get away from it. Thanks for the tip! >