I have a Windows 7 Ultimate x86_64 machine, which is failing to access a network samba server. I launch the "Run" dialog, and type in \\192.168.x.x so I am bypassing DNS and NetBIOS name resolution, and broadcast discovery, just going directly to the server IP address. I ran wireshark and found that the client is trying to connect to the server on port 80, not 445. (This of course fails because the server is not listening on 80; the server is only running samba and nmbd etc, so only port 445 and 137-139 are applicable).
The error message is: "Windows Cannot Access \\192.168.x.x" and when I click "See Details" it says "Error Code 0x800704cf The network location cannot be reached" I confirmed that "Client for Microsoft Networks" is present, and enabled. I even removed it (was forced to reboot) and reinstalled it. No effect. I disabled IPv6, no effect. I confirmed the "WebClient" service is not running. (It is set to Manual, and it's not Running). I confirmed the "TCP/IP NetBIOS Helper" service is running. (It is set to Automatic, and it's Running.) Of course I have rebooted and retried. (Several times and several ways). The problem seems to exist with an old patch level, and also continues to exist after applying all Windows Updates. Any ideas would be greatly welcome. Why would windows attempt to use port 80 (webdav) instead of port 445 (samba/smb/cifs) to connect file explorer to a UNC path?
_______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
