Windows + samba +”network path not found” = teh madness
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Windows + samba +”network path not found” = teh madness
Trying to get my XP-pro machine to connect with an Ubuntu 6.1 (Edgy Eft) samba server. The most I can see is the Samba server’s name listed in the Microsoft Windows Network. Trying to access it gives me a “The network path was not found” error. (pic below)
Someone had a similar problem on this board http://www.linuxquestions.org/questi...ad.php?t=44715, which was solved by turning the firewall off. I’ve tried turning my XP firewall off, made sure Firestarter (ubuntu’s graphic firewall program), and/or iptables are not running, and I still have the error. My router has a firewall which I don’t think can be turned entirely off, but I’ve tried opening ports 137-138 (udp) and 139 (tcp)and 448 (tcp) in my router’s firewall. (pic below)
Testparm clears the smb.conf, which was generated by SWAT. My samba server has a static IP 192.168.0.10 (hmm…which is in the range of my DHCP server’s addresses 2-51. Is that a problem?).
This great site http://www.linuxhomenetworking.com/w...roubleshooting
Has a list of troubleshooting things to try. Here’s what works (and doesn't):
>From the Samba Server try to:
>1. Ping the server's IP address and loopback address (127.0.0.1)
>2. Ping the client's IP address
Yes to both.
>3. Ping the client using its DNS name
No. Is this just the client name?
>4. Telnet to all the IP addresses on the server on port 139
No.
>Next, from the Samba Client (winXP) try to:
>1. Ping the client's IP address and loopback address (127.0.0.1)
>2. Ping the server's IP address
Yes to both.
> 3. Ping the server using its DNS name
Again, d/n work. Is this just the server name?
>4. Telnet to all the IP addresses on the server on port 139
No. can’t get puTTY to get through
Running 'smbclient -L hostname' shows the appropriate shares. I'll post my smb.conf in another post. I've spent days and now this is driving me crazy...
Here's my smb.conf for the bold, pared as intelligently as I could. I have created users/passwords for the shares, and they are the same as my XP passwords (even did the "manage my network passwords" in the xp ctrl panel).
# Samba config file created using SWAT
# from 192.168.0.10 (192.168.0.10)
# Date: 2007/02/10 21:30:10
[global]
workgroup = MSHOME
realm =
netbios name = UMAIR-DESKTOP
server string = %h server (Samba, Ubuntu)
obey pam restrictions = Yes
passdb backend = tdbsam
bind interfaces only = No
security = USER
auth methods =
encrypt passwords = Yes
update encrypted = No
client schannel = Auto
server schannel = Auto
allow trusted domains = Yes
password server = *
smb passwd file = /etc/samba/smbpasswd
private dir = /etc/samba
passdb backend = tdbsam
root directory =
guest account = nobody
enable privileges = No
smb ports = 445 139
disable netbios = No
nt pipe support = Yes
nt status support = Yes
announce version = 4.9
announce as = NT
name resolve order = lmhosts wins host bcast
client signing = auto
server signing = No
client use spnego = Yes
enable asu support = Yes
paranoid server security = Yes
preferred master = Auto
local master = Yes
domain master = Auto
browse list = Yes
enhanced browsing = Yes
dns proxy = No
wins proxy = No
wins server =
wins support = No
wins hook =
wins partners =
eventlog list =
config file =
preload =
lock directory =
pid directory = /var/run/samba
remote browse sync =
socket address = 0.0.0.0
homedir map = auto.home
path =
username =
invalid users = root
valid users =
admin users =
guest only = No
guest ok = No
only user = No
hosts allow =
hosts deny =
[printers]
comment = All Printers
path = /tmp
create mask = 0700
printable = Yes
browseable = No
good catch. i do mean 445, and the mistake was propagated into the router settings. re: SElinux, i'm actually not sure, but it does look like all the appropriate packages seem to be installed in ubuntu by default.
good thoughts. smbd and nmdb are in the process list. smbclient on the localhost shows the appropriate shares, which i assume w/n work unless the samba server is running.
edit: by direct connection, you mean connecting the ethernet ports of the cpus directly, with the router out altogether? i'm not sure what would have to change from a config standpoint to test it out, but i can try....
I just fixed this problem for myself, but found this posting while looking for the solution. For me, the solution was to disable SELinux security.
It sounds like you are also setting up a personal network behind a firewall, as I am. I have very strict firewall settings on my switch/gateway to the internet so the SELinux level of protection on each machine is certainly overkill anyway.
I am running Fedora Core 6. To turn off SELinux, I:
* Started X
* System > Administration > Security Level and Firewall
* SELinux tab
* Disable
* OK
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.