Hello all, thanks for the replies!
Reeves, Gary wrote:
Have a look here http://support.microsoft.com/kb/832161
Yes, I have read that article already. It does seem related, but...
With webclient activated the Network Provider Order lists Web Client Network before it lists Microsoft Windows Network. Which is what I believe you are seeing.
...the network provider order does list "Microsoft Windows Network" before "Web Client Network", on both the machines that work and the machines that fail. Furthermore. on machines that work, I can change the order (ie. put "Web Client Network" first) and they continue to work.
I did try disabling the Web Client service as mentioned in the KB article. In this case the filer sees virtually no traffic from the client at all (no SMB/CIFS, no HTTP, just some ICMP pings)
Langdon, Laughlin T. wrote:
Have you tried the mapping with a fully qualified domain name?
The behavior is the same with short name and fqdn.
Ryan Dorman wrote:
Do you get a response from NBTSTAT -a for the short name?
Yes.
Is there a message in the logs saying that a WINS registration succeeded and do you see the entry on your WINS server (if you have one)?
Client or server? The server is definitely there. The client has been moved back to the wired network (where the drive mapping works properly) so the entry (if it existed) has been overwritten. (BTW, the WINS server is Samba)