Fileshares won't work with name but will with ip address? DNS ok.

[chazzy2501]

I have a server called "backupserver2" it's ip address is "10.44.8.6/22" I've disabled the firewall for testing and the issue still occurs. If I put "\\backupserver2\" into the run command the resource is not found. if I put "\\10.44.8.6\" it works fine.

 

I've done all the DNS testing I can think of. The forward and reverse lookups are correct on both DNS servers. The nslookup confirms the ip address. you can ping the server name and it resolves to the correct ip address and pings. I've flushed the DNS anyway on both the server and client and the issue remains?

 

All other server shares on other servers work correctly..

 

Anything I haven't though of?

 

Oh I've rebooted the server and tried other clients and it still happens. it is a 2003r2 server and the clients are win7 and server2008

Edited November 2, 2012 by chazzy2501
TYPO

[glennda]

You mention 2 server names is that just a typo?

[plexer]

Does it work via the fqdn of the server?

 

Ben

[chazzy2501]

typo backupserver 2

 

YES... The FQDN works! Why?

[m25man]

I posted this a long while back,

http://www.edugeek.net/forums/windows-7/84160-problems-accessing-nas-windows-7-clients.html#post741942

 

It explains the behaviour dependent on the direction of the connection. The Keberos/NTLM2 issue crops up time and again and a bit of packet capture should prove it.

 

How you correct it will depend on how you can control the security policy elements.

In a domain environment the settings can be easily handled through GP's but we all know that Win7 clients don't like to play with 2003 DCs so this can be a real pain without a 2008 DC where all of the policy elements match.

 

Dumbing your security down to Lanman is not where you want to go really other than for testing.

If your DNS/RDNS is healthy and the fix works for you take it as proof that its time to update your 2003 servers.