Network share: big difference if netbios name or FQDN is used?
Hello,Here is my setup:- Win2k8 Server SP2 (named master)- Windows 7 clientDepending on the name I use to reach my server I get different behavior:- If I use the NetBIOS name (\\master) everything works fine. I can drag & drop without warning from the shares and I can see the free space of the network drives attached to those shares under "Computer"- But, if I use the FQDN instead (\\master.mysweethome.local) everything goes wrong. Indexation is broken, I get a warning when I try to drag & drop files from the server, and finally I am unable to see the free space from the attached network drive from "Computer"Here is the warning I get with the FQDN: http://i36.tinypic.com/hwiwhx.jpgAnd here is a print screen of my "Computer" with two network drives pointing to the same network share, but using both method (NetBIOS and FQDN): http://i36.tinypic.com/f3vz2o.jpgI would love to get some explanations about this behavior. Is it a bug or a feature? Is there a way to alter settings related to this?Thank you,This issue is maybe related to the one reported here: http://social.msdn.microsoft.com/Forums/en/windowsdesktopsearchhelp/thread/85525c46-1ab5-46e1-a288-e36561a6ffab (indexation broken with DFS shares). If DFS redirect the client to the server's FQDN it may break indexation
October 10th, 2009 11:58pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics