I've got a real issue that needs rectifying ASAP.
Last night, I was migrating some shares from one server to another (source we'll call SBS2K3 as it is SBS2003 and the destination server we'll call S002, which is a Win 2K3 R2 box). Everything seemed to go without a hitch, I changed the login scripts for the users, tested it and everything was working.
This morning, something had changed and I do not know what. The SBS2K3 box is also the DC (obviously) and S002 is just a file, print and backup server. The problem I have is that the SBS2K3 box does not show any shares if you browse to it by just using the UNC path \\SBS2K3, except one, 'Users' which is a share I unshared last night.
If I browse to the FQDN - \\SBS2K3.exampledomain.local then I can see all the printers, and administrative shares etc (no Users share).
This is a real problem, as clients are no longer able to access the group policies or the SYSVOL/NETLOGON shares - hence the new login scripts are not executing. I have tried adding connection specific DNS suffix etc to no avail.
Strangely, if I log on with any user account onto any static TCP/IP configured machine (i.e. another server, the S002 server etc), then I can view all the shares by just using the UNC path \\SBS2K3 with no domain suffix. Any DHCP client has the issue described above. If you compare the IPConfig output between the servers and the DHCP clients, the output is identical bar the IP of the device. Also, if I browse by IP, all the shares are listed.
Bear in mind that yesterday, ALL was working fine. There are no DNS errors in the logs, and there has been no change in the DHCP options or the static setup of any box. The only thing that changed on the DC was I unshared the shares I'd migrated, and I'd changed the logon scripts.
Now I know what everyone is going to say, it's a DNS or WINS issue. It was working yesterday - and also the the SBS2K3 name resolves to the correct IP through NSLookup etc - and connecting by IP actually works. Also, I can connect to SBS2K3 by using just '\\SBS2K3' but it just displays the incorrect share (one that shouldn't exist). I have restarted the server service and the server itself to no avail.