Problems accessing server shares rfalken 5/11/2007 7:52:02 AM Hello, I get the following error from one of my servers trying to access another specific server. "Windows cannot find "\\aa1'. Check the spelling and try again,..." If i try to ping aa1 there is no problems, and it returns the FQDN. If i try to access the server my aa1.comp.local then i also can access it. I tried to flush the dns from this server but no luck there either. Anyone have a comment on what i could try ? Kind Regards Rene

Re: Problems accessing server shares Nick Domukhovsky <ndomukhovsky[ at ]ot.ru> 5/11/2007 9:45:00 AM [Quoted Text] > Hello, > > I get the following error from one of my servers trying to access another > specific server. > > "Windows cannot find "\\aa1'. Check the spelling and try again,..." > > If i try to ping aa1 there is no problems, and it returns the FQDN. If i try > to access the server my aa1.comp.local then i also can access it. > > I tried to flush the dns from this server but no luck there either. > > Anyone have a comment on what i could try ? > > Kind Regards > Rene When you typing \\<name> you using NetBIOS name system to resolve this name. All your tests check DNS functionality. You can test NetBIOS name resolution with command "nbtstat -a <name>". But remember - if you have more then one network segment and you have not WINS server you will face name resolution problems, because in such configuration you will be unable resolve names of servers from other segment. -- With best regards Nickolay Domukhovsky, MCSA

Re: Problems accessing server shares rfalken 5/11/2007 10:37:00 AM When i do that i get nbtstat -a aa1 Local Area Connection: Node IpAddress: [172.16.1.23] Scope Id: [] NetBIOS Remote Machine Name Table Name Type Status --------------------------------------------- AA1 <00> UNIQUE Registered AA <00> GROUP Registered AA1 <03> UNIQUE Registered AA1 <20> UNIQUE Registered INet~Services <1C> GROUP Registered IS~AA1.... <00> UNIQUE Registered AA <1E> GROUP Registered MAC Address = 00-07-E9-C8-42-BA Then it should be work right ?

Re: Problems accessing server shares Nick Domukhovsky <ndomukhovsky[ at ]ot.ru> 5/11/2007 11:10:46 AM [Quoted Text] > When i do that i get > > nbtstat -a aa1 > > Local Area Connection: > Node IpAddress: [172.16.1.23] Scope Id: [] > > NetBIOS Remote Machine Name Table > > Name Type Status > --------------------------------------------- > AA1 <00> UNIQUE Registered > AA <00> GROUP Registered > AA1 <03> UNIQUE Registered > AA1 <20> UNIQUE Registered > INet~Services <1C> GROUP Registered > IS~AA1.... <00> UNIQUE Registered > AA <1E> GROUP Registered > > MAC Address = 00-07-E9-C8-42-BA > > Then it should be work right ? Yes. Should... No more ideas for now... -- With best regards Nickolay Domukhovsky, MCSA

RE: Problems accessing server shares Ryan Hanisco 5/13/2007 3:03:00 AM Hi rfalken, When you try to find a server or workstation by UNC path (e.g., \\aa1) your computer doesn't necessarily try to find it using DNS. If you don't have your node typoe set to hybrid (0x8) in your DHCP it may try broadcasting across your network for the netbios master list or WINS. Try hitting the workstation by ping and then pinging the full address: ping aa1.domain.com (or whatever) If you can resolve the name to an IP address, the DNS is working fine. You can even verify this with NSLOOKUP. The error you are getting might be from a messed up lookup. It can also occur if you don'd have file and print sharing on or if there are no shared resources on the computer. Finally, restrictions in the windows firewall or another security service (norton/ symantic, mcafee, etc.) can deny requests and stop the service. I don't have enought information to tell you exactly what to do, but hopefully this will put you on the right track. -- Ryan Hanisco MCSE, MCTS: SQL 2005, Project+ Chicago, IL "rfalken" wrote: [Quoted Text] > Hello, > > I get the following error from one of my servers trying to access another > specific server. > > "Windows cannot find "\\aa1'. Check the spelling and try again,..." > > If i try to ping aa1 there is no problems, and it returns the FQDN. If i try > to access the server my aa1.comp.local then i also can access it. > > I tried to flush the dns from this server but no luck there either. > > Anyone have a comment on what i could try ? > > Kind Regards > Rene