Windows7 Cannot see Samba Shares after Client For NFS is Installed
Hoping to Claify my earlier post that was not answered.If you have Linux machines running samba, they can share folders with Windows and Mac systems.Our particular shares have worked for years. They worked well in Windows 7 until we installed Client For NFS. Now the NFS shares form the Linux systems work, but the Windows7 Networking shares fail with a "path not found (53)" error displayed when you type net view \\samba-server-name-here.It acts like the NFS client software disables the ability of Windows Networking to resolve thepath of the Linux system.net view and the windows explorer continue to list systems with samba shares,but it produces errors if you try to open these shares.Using XP on VirtualPC on the same Windows7 system, the (virtual) XP that is sharing the network card with the Windows7 Host can use the samba shares normally, same computer, same Windows7, same network card. All of the shares are OPEN and need no authentication on any system.This is a show stopper for NFS Client on Windows 7 in my opinion.
September 4th, 2009 5:28pm

This behavior occurs if firewall block the access. Please temporary disable it and check the result. If the issue persists, please let us know if you could access the Samba computer after entering \\[IP address]. Also, please export two reports: 1. IP configuration report. Please enter ipconfig /all > %userpofile\desktop\ipconfig.txt in command prompt, then open the file ipconfig.txt on Desktop and past the contents in your post. 2. Routing report. Please enter route print > %userpofile\desktop\route.txt in command prompt, then open the file route.txt on Desktop and past the contents in your post. Also please let us know what is your DNS server. If it is a router or a DNS server that is installed on a computer.Arthur Xie - MSFT
Free Windows Admin Tool Kit Click here and download it now
September 8th, 2009 12:37pm

===========================================================================Interface List11...00 23 54 51 43 f1 ......Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller #210...00 23 54 51 43 f2 ......Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller 1...........................Software Loopback Interface 112...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter13...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface15...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2=========================================================================== IPv4 Route Table===========================================================================Active Routes:Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.102 10 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 192.168.0.0 255.255.255.0 On-link 192.168.0.102 266 192.168.0.102 255.255.255.255 On-link 192.168.0.102 266 192.168.0.255 255.255.255.255 On-link 192.168.0.102 266 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 192.168.0.102 266 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 192.168.0.102 266===========================================================================Persistent Routes: None IPv6 Route Table===========================================================================Active Routes:If Metric Network Destination Gateway13 18 ::/0 On-link 1 306 ::1/128 On-link13 18 2001::/32 On-link13 266 2001:0:4137:9e50:10f1:256f:bd24:51b8/128 On-link10 266 fe80::/64 On-link13 266 fe80::/64 On-link13 266 fe80::10f1:256f:bd24:51b8/128 On-link10 266 fe80::2060:5943:f39e:fab0/128 On-link 1 306 ff00::/8 On-link13 266 ff00::/8 On-link10 266 ff00::/8 On-link===========================================================================Persistent Routes: NoneWindows IP Configuration Host Name . . . . . . . . . . . . : Demo Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection 2: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller #2 Physical Address. . . . . . . . . : 00-23-54-51-43-F1 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller Physical Address. . . . . . . . . : 00-23-54-51-43-F2 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::2060:5943:f39e:fab0%10(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.0.102(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Tuesday, September 08, 2009 8:45:33 AM Lease Expires . . . . . . . . . . : Wednesday, September 09, 2009 8:45:33 AM Default Gateway . . . . . . . . . : 192.168.0.1 DHCP Server . . . . . . . . . . . : 192.168.0.1 DHCPv6 IAID . . . . . . . . . . . : 251667284 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-11-14-13-E2-00-23-54-51-43-F2 DNS Servers . . . . . . . . . . . : 66.219.156.2 209.143.0.10 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter isatap.{1158BEE5-968D-4338-AA81-D8E9E2FE7ECB}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Teredo Tunneling Pseudo-Interface: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:10f1:256f:bd24:51b8(Preferred) Link-local IPv6 Address . . . . . : fe80::10f1:256f:bd24:51b8%13(Preferred) Default Gateway . . . . . . . . . : :: NetBIOS over Tcpip. . . . . . . . : Disabled Tunnel adapter isatap.{A771F4AD-F677-4DEF-83C2-C70667F7D75B}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2 Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : YesServer Name Remark -------------------------------------------------------------------------------\\AVID2K \\CRISTINA Graphic & Photos \\CTMAC CTMAC \\DEMO Demo1 \\FLAME2008 flame2008 \\MACPROVMWARE \\MEDIAMASHER \\MUSIC \\NT-SERVER \\OCTANE Samba 2.2.8a.2 \\OCTANE3 Samba 3.0.20a \\PS0A7B72 \\RACK rack \\SHOP Mr.Ugly \\SMOKE1 Smoke1:Samba 2.2.8.1 \\SMOKE2 Samba Server \\SMOKE3 Smoke3 \\SUITESMOKE SuiteSmoke \\TESTBED \\TOSH06 \\WIN2000 The command completed successfully. THIS OSX LEOPARD with NFS and SAMBA WORKS !CTMAC C:\Users\CT>net view \\ctmacShared resources at \\ctmac Share name Type Used as Comment -------------------------------------------------------------------------------ct mac's public folder Disk CT MAC's Public Folder developer's public folder Disk Developer's Public Folder macpro Disk macpro macraid Disk MACRAID The command completed successfully.C:\Users\CT>showmount -e \\ctmacExports list on ctmac:/Volumes/MACRAID All MachinesRED HAT Linux with NFS and Samba SHARES, ONLY the NFS SHARES WORK WHEN CLIENT FOR NFS IS INSTALLED.C:\Users\CT>ping smoke2 Pinging smoke2 [192.168.0.48] with 32 bytes of data:Reply from 192.168.0.48: bytes=32 time<1ms TTL=64C:\Users\CT>net view \\smoke2 > c:\users\ct\desktop\net_view_LINUX_with_nfs+samba.txtSystem error 53 has occurred.C:\Users\CT>net view \\192.168.0.48Shared resources at \\192.168.0.48 Samba Server Share name Type Used as Comment ----------------------------------------------XFER DiskThe command completed successfully. The network path was not found.C:\Users\CT>showmount -e \\smoke2Exports list on smoke2:/usr/discreet */usr/xfer */sata/ *As I said, On VirtualPC under the same copy of Windows7, the same linux windows networking (SAMBA) shares work with no problem.All of the NFS + SAMBA machines ( MAC, Linux and Irix ) have STATIC IP ADDRESSES.They are identified (DNS) with /etc/hosts files on theUnix systems, and windows networking finds themfrom their SAMBA servers, as you can see on the net view commandand ping above.Using the \\IP address rather than the \\servername seems to work after I changed the TCP-IP protocol -advanced -WINS adapter setting from default to USE NETBIOS OVER TCP-IP.The \\192.168.0.48 shares do not show up in the network explorer until I type it manually on anaddress bar .....Please remember, all of this worked fine until Client for NFS was installed. I can try an win\sys32\drivers\etc\hosts or lmhosts.sam entries if need be, but these weren't needed before, the NFS shares work and ping and net view both find the hosts by name, so I see this as a bug introduced by the NFS client for Windows 7. Lots of Stuff, thanks for Listening
September 8th, 2009 5:59pm

1) Firewall settings had no effect.
Free Windows Admin Tool Kit Click here and download it now
September 8th, 2009 6:14pm

Hi, As you can see, the DNS servers are changed. There are two servers, 66.219.156.2 and 209.143.0.10. It seems that they are on the NFS server side. There should be another DNS server 192.168.0.1, which is your router. May be there are problems on the NFS client installation so it cannot correctly configure the DNS for the NIC. You may try to manually add the DNS server 192.168.0.1 and check the result. Arthur Xie - MSFT
September 9th, 2009 8:03am

The local router DNS does not apply because a) all the other network servers are 'findable'b) A mac OSX Leopard with NFS and Samba shars works finec) pinging all the names worksd) net view worksE) I tried it and it doesn't matter !Microsoft Windows [Version 6.1.7100]Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\CT>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : Demo Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection 2: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller #2 Physical Address. . . . . . . . . : 00-23-54-51-43-F1 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller Physical Address. . . . . . . . . : 00-23-54-51-43-F2 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::2060:5943:f39e:fab0%10(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.0.102(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Tuesday, September 08, 2009 8:45:33 AM Lease Expires . . . . . . . . . . : Thursday, September 10, 2009 9:58:36 AM Default Gateway . . . . . . . . . : 192.168.0.1 DHCP Server . . . . . . . . . . . : 192.168.0.1 DHCPv6 IAID . . . . . . . . . . . : 251667284 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-11-14-13-E2-00-23-54-51-43-F2 DNS Servers . . . . . . . . . . . : 192.168.0.1 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter isatap.{1158BEE5-968D-4338-AA81-D8E9E2FE7ECB}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Teredo Tunneling Pseudo-Interface: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:10f1:256f:bd24:51b8(Preferred) Link-local IPv6 Address . . . . . : fe80::10f1:256f:bd24:51b8%13(Preferred) Default Gateway . . . . . . . . . : :: NetBIOS over Tcpip. . . . . . . . : Disabled Tunnel adapter isatap.{A771F4AD-F677-4DEF-83C2-C70667F7D75B}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2 Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes C:\Users\CT>net view smoke2System error 53 has occurred. The network path was not found. C:\Users\CT>showmount -e smoke2Exports list on smoke2:/usr/discreet */usr/xfer */sata/ *C:\Users\CT>net view ctmacShared resources at ctmac CTMAC Share name Type Used as Comment -------------------------------------------------------------------------------ct mac's public folder Disk CT MAC's Public Folderdeveloper's public folder Disk Developer's Public Foldermacpro Disk macpromacraid Disk MACRAIDThe command completed successfully. C:\Users\CT>showmount -e ctmacExports list on ctmac:/Volumes/MACRAID All MachinesThis is a subtle problem because it works with some server typeswith BOTHNFS AND SAMBA servers and not others and only on Windows 7.I added 192.168.0.48 to BOTH LMHOSTS.SAM and HOSTS, and that did not fix the problem, so DNS is not the problem. I also find this kind of interesting ...... net view ctmac and net view \\ctmac produce DIFFERENT RESULTS ....C:\Users\CT>net view \\ctmacShared resources at \\ctmac CTMAC Share name Type Used as Comment -------------------------------------------------------------------------------ct mac's public folder Disk CT MAC's Public Folderdeveloper's public folder Disk Developer's Public Foldermacpro Disk macpromacraid Disk MACRAIDThe command completed successfully. C:\Users\CT>net view ctmacShared resources at ctmac CTMAC Share name Type Used as Comment -------------------------------------------------------------------------------developer's public folder Disk Developer's Public Foldermacpro Disk macpromacraid Disk MACRAIDThe command completed successfully. C:\Users\CT>showmount -e ctmacExports list on ctmac:/Volumes/MACRAID All Machines C:\Users\CT>showmount -e \\ctmacExports list on ctmac:/Volumes/MACRAID All MachinesIf there are any tools I can use to help clarify the exact issue, or if I should submit this issue as a BUG report somewhere, please let me know.
Free Windows Admin Tool Kit Click here and download it now
September 9th, 2009 5:25pm

nbtscan shows the ip address and the workstation name for the problem shares, just like this:192.168.0.48 WORKGROUP\SMOKE2 SHARING SMOKE2 <00> UNIQUE Workstation Service SMOKE2 <03> UNIQUE Messenger Service<3> SMOKE2 <20> UNIQUE File Server Service WORKGROUP <00> GROUP Domain Name WORKGROUP <1e> GROUP Browser Service Elections 00:00:00:00:00:00 ETHER smoke2all nix boxes have ETHER 00:00:00:00:00:00 and work fine in XP.
September 9th, 2009 6:07pm

Hi, You may try Network Monitor 3.3 to monitor the whole process. 1) Download NetMon3.3 from the following website and install it on the computer 2) Launch NetMon3.3.3) In the Microsoft Network Monitor 3.3 window, click Create a new capture tab 4) In the new tab, select all the Network Adapters in the Select Networks window.5) Go to sync time page. Then, switch to Network Monitor, press F5 to start NetMon.6) Try to sync time.7) Go back to the NetMon window and press F7 to stop the NetMon.8) Press Ctrl+S to save the Netmon file named test. You may try to find some clues. Also you can submit the whole log in the following network space. Microsoft Services File Transfer Password is zHMiOioS7lZx-YCArthur Xie - MSFT
Free Windows Admin Tool Kit Click here and download it now
September 11th, 2009 10:03am

??? Go to sync time page....Are these the instructions if you cannot contact a time server ? I assume you mean capture a net view on a working and non-working samba share ......Thanks, I will try it....
September 11th, 2009 8:13pm

We found that an old NT-4 server, and Linux and Irix servers SMB shares will not work by name with Windows7-64 if Client For NFS is installed. These shares worked well before client for NFS was installed (On Windows7) The NFS shares on these systems do work. You can ping all the servers by name. The SMB shares can be browsed by IP address but not by name. ie NET VIEW produces a list of ALL the server names. NET VIEW smoke2 produces ERROR 53, path not found NET VIEW 192.168.0.48 ( the ip address of smoke2) works normally. showmount -e smoke2 works normally. Netmon3 shows on systems that work the DESTINATION is shown by NAME and a series of SMB commands follow. On systems that fail by name, Netmon3 shows net view immediately translates the name to an ip address and begins to send commands to the NFS RPC instead of the SMB server.
Free Windows Admin Tool Kit Click here and download it now
September 12th, 2009 12:04am

Hi, Files are received. We will reply after working out a conclusion.Arthur Xie - MSFT
September 14th, 2009 1:17pm

Hi, We can see that the computer name is already resolved. Therefore it should not be an name resolution issue. It seems that when you net view with the computer name, the server cannot pass the NTLM authentication. In Windows Vista and Windows 7 the default NTLM authentication level is changed. Please refer Network security: LAN Manager authentication level Please try to change the authentication level to Send LM & NTLM - use NTLMv2 session security if negotiated on the Windows 7 computer.Arthur Xie - MSFT
Free Windows Admin Tool Kit Click here and download it now
September 15th, 2009 1:07pm

Hello Arthur,I made this change and it had no effect, but we did not expect it to. 1) These shares worked fine before Client for NFS was Installed.2) These shares are OPEN and require no authentication.I amsure that Client for NFS has caused a change to the system that damaged the ability of the system to connect to some SMB shares by name.It is clear from the netmon3.3 logs that every share that works is queried by name, and every one that doesn't is queried by ip address. As soon as the IP address is used, it begins to try to access the "Sun RPC" protocol, which is the NFS server. As you know, the Sun RPC will not service LANMAN shares.Are there any other support options available from Microsoft that I can use to tackle thisBUG in Windows 7.
September 15th, 2009 4:15pm

Hi, Did anyone on this thread end up finding a resolution for this issue?? I appear to be experiencing the same problem. But after hours of searching so far haven't found a solution. Win 7 64bit, can't connect to samba by hostname (but can resolve host name if pinged) You just get a infinate loop of 'enter your network password'.However connecting via ip address, connects happily. Domain authentication works normally as it does with our XP machines. *Tried all the LM & NTLM local policy stuff, and the 128bit encryption disabling
Free Windows Admin Tool Kit Click here and download it now
April 15th, 2010 4:43am

I've got Windows 7 on a laptop and Fedora 12 on a server. Everything worked fine until I rebooted the server. For reasons I've yet to uncover the system was being added to the hosts file (from which I also build the local DNS domain) against the 127.0.0.1 loopback address. The Windows client would resolve the server to it's own local loopback, no wonder it wouldn't connect! I could connect with the IP address, thanks for the hints. If anyone else is still stuck check all your name resolution is correct. Thanks, Mark, working again!
May 29th, 2010 3:00am

I have the "System error 86" ..."The specified network password is not correct" problem connecting to a read only samba share on a compaq 64 Unix server. Testing on Windows 7 64 bit and Windows 7 32 bit (both Enterprise Edition) machines gives the same error. Connecting with an XP virtual machine on the 64 bit W7 machine works. Security settings changed to "Send LM & NTLM -use NTLMv2 session security if negotiated" and the "Minimum session security for NTLM SSP..." is not defined - no selection. The server has been added to "Server Exception" then removed because it made no difference. I have attempted using the IP address for the server with no success.
Free Windows Admin Tool Kit Click here and download it now
June 9th, 2010 5:17pm

Rberk, hopefully this can shed a little light on your issue. I've noticed the same propblem with XP for quite a while now. Once I install the client, it seems Windows defaults to NFS as opposed to CIFS. I find that in XP I can use the "NET USE" command to mount the share as CIFS and it will work properly from there. This appears to only be a problem when the server shares the same folder as both NFS and CIFS, and I agree with your assessment that it appears to be a bug in the NFS client software. I've been searching for quite a while now for a way to convince windows to try CIFS first. I'd be interested in any other information you may have on this issue. Bryan
July 8th, 2010 10:25am

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

Other recent topics Other recent topics