Hi, I try to connect to my samba server from an W2k client. If I connect to a share \\home\myshare it is possible to browse and do all the other things. If I try to get an overview of the whole domain i.e. trying to connect to my Network the error message "Network Path not found" occurs. Any suggestions ? Thanks Tom
Greetings!! I have installed Samba on a UNIX station running sol 2.6 and have connected to 3 NT workstations. I was able to access the designated shares from each station but have just recently lost the ability to access the 3rd NT machine. The network connection was lost and when we try to map the shares in the network neighborhood, we get errors such as Network Path Not Found, or that our server name does not exist, or that the server is not accessible. The server name is Ptolemy. Ptolemy does show up in the network neighborhood on Braun. We are able to ping the suspect machine named BRAUN. Braun can also ping the server. Braun can see the shares of the other NT machines. Performing a net view \\ Ptolemy yields the same network error. As I mentioned before we had it running fine. The problem came when we changed the smb.conf for some browsing options. When we lost the connection to Braun, I used the backup of a smb.conf that we had the NTs seeing the shares. Its like Ptolemy does not want to share with Braun. Have you heard of this happening and is there a way to fix it? Thanks Pat Easton Member of the Technical Staff Litton/TASC 703 633-8300 x 4391
All, We have had samba (2.0.0) running here for a number of years without any problems. However, we will soon be getting some windows 2000 machines added to the network and there will be need to upgrade to a newer version. In preparation for this move I decided to convert our current encryted passwords = no to yes as I am much happier having these things encrypted. I edited smb.conf and added the line encrypt passwords = Yes, killed the smbd and restarted it. Ran testparm to check the change (no problem). Tested the connection on my test machine which did not have the plain text registry hack on it and it was fine. Happy with the test I reverted back to no encryption and check with testparm to confirm. But, now I cannot connect to the samba server from the normal machines as when I try to browse from the Windows Exploreron NT SP5 I get the following error: "The network path was not found." Still works fine on Win98 machine here and I can still connect to other windows machines and samba servers here from the WINNt machines. Does anyone have any ideas what has happened ? Julian
Julian Sinclair wrote:> All, > > We have had samba (2.0.0) running here for a number of years without any > problems. However, we will soon be getting some windows 2000 machines > added to the network and there will be need to upgrade to a newer > version. > > In preparation for this move I decided to convert our current encryted > passwords = no to yes as I am much happier having these things > encrypted. > > I edited smb.conf and added the line encrypt passwords = Yes, killed the > smbd and restarted it. Ran testparm to check the change (no problem). > Tested the connection on my test machine which did not have the plain > text registry hack on it and it was fine. > > Happy with the test I reverted back to no encryption and check with > testparm to confirm. > > But, now I cannot connect to the samba server from the normal machines > as when I try to browse from the Windows Exploreron NT SP5 I get the > following error: > > "The network path was not found." > > Still works fine on Win98 machine here and I can still connect to other > windows machines and samba servers here from the WINNt machines. > > Does anyone have any ideas what has happened ? > > Julian> All, > > Have continued playing with the setup here. Changed log level of samba to > > 10 but of course nothing is being added because the error is occuring > even > before the request gets to samba. > > Opened up command prompt on nt. > did a tracert to the samba server - no problems. > did an nslookup to the samba server - no problems. > > Tried using net use X: \\[fqdn]\d1 > > Asked for password and connected without a problem. Even more confused > now. > For now this as least means that I can map drives as required but cannot > browse the samba server from windows explorer. Am I missing something > really obvious here ? > > Julian > > >
I have searched the web and I am completely out of ideas. I have RH 7.2 installed with samba 2.2.4-2. I can currently ping the linux box with the ip and netbios name. I can ping all of the w2k systems with ip and netbios name. I can see the linux box in network neighborhood. I just can not see my shared folders I have also turned of ipchains and iptables. I have tried with encrypted passwords on and off. Please help.. Thanks, Mike --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.372 / Virus Database: 207 - Release Date: 6/20/2002 -------------- next part -------------- HTML attachment scrubbed and removed
I'm trying to get samba running on an IBM-Compatible to be viewable from a Windows2000 Network Neighborhood browser. I keep getting the error from the windows 2000 client \\SAMBACOMPUTER was not available The network path was not found Even though it shows up fine on the windows browser the error log says "passdb/bdb_smbpasswd.c:pdb_betsampwnam(1367) unable to open passdb database. Though I don't think they are related Any Ideas? -------------- next part -------------- HTML attachment scrubbed and removed
I'm trying to get samba running on an IBM-Compatible to be viewable from a Windows2000 Network Neighborhood browser. I keep getting the error from the windows 2000 client \\SAMBACOMPUTER was not available The network path was not found Even though it shows up fine on the windows browser the error log says "passdb/bdb_smbpasswd.c:pdb_betsampwnam(1367) unable to open passdb database. Though I don't think they are related Any Ideas? -------------- next part -------------- HTML attachment scrubbed and removed
I've searched up and down on Google and Google Groups for an answer to this question, and I found that it's asked a lot, but I didn't find many answers. My W2K box can find the Linux samba server but when I click on it, it gives me "Network path could not be found." Some of the answers I found said to include the subnet mask (255.255.255.0), and I tried that with Swat, but when I went to restart smbd and nmbd, the first succeeded but the second remains "not running," whether I click "start" or "restart." What's going on? Feel free to point to the appropriate place in TFM/mailing list archive/website/faq. Thanks, -- Marc Adler
Hi group I have been toying with samaba for a while now and I only manage to get it to work haphasardly. The problem I have is I cannot see the shares i have created on the Samba machine, I get a Network path not found message. Here is what I have so far: 1. Samba installed and running. Share have been created. Samba macchine is named Linux 2. On the samba machine, smbclient -L Linux returns the shares I have created. 3. However, the command net view Linux or net use \\linux\tmp on any other win machine returns "network path not found". 4. Also, the command nmblookup Linux on the samba machine returns "name_query has not found name Linux" but nmblookup Winmachine retruns the IP of that machine. To help you, here is the set up I have: - windows network - PDC is a win2000 pro machine, also DHCP server smb.conf file looks somewhat like this: [global] netbios name = Linux workgroup = myworkgroup encrypt passwords = yes security = share guest = ftp [public] path = /tmp public = yes guest ok = yes guest only = yes browseable = yes read only = no Can anyone help me with this problemm. I have tried the trouble shooting from the o'reily book and it seems that I have a netbios name "recongnition" problem that is not covered in the o'reily book. The only thing I have not looked at is the password issues. Sonce I'm not restricting access to my share I did not think it was necessary. Thanks all, Marc
Are you running both smbd and nmbd? nmbd handles the netbios queries. On Fri, 2003-10-24 at 14:33, Marc Drouin wrote:> Hi group > > I have been toying with samaba for a while now and I only manage to get it > to work haphasardly. > > The problem I have is I cannot see the shares i have created on the Samba > machine, I get a Network path not found message. > > Here is what I have so far: > > 1. Samba installed and running. Share have been created. Samba macchine > is named Linux > > 2. On the samba machine, smbclient -L Linux returns the shares I have > created. > > 3. However, the command net view Linux or net use \\linux\tmp on any other > win machine returns "network path not found". > > 4. Also, the command nmblookup Linux on the samba machine returns > "name_query has not found name Linux" but nmblookup Winmachine retruns the > IP of that machine.-- Nick THOMPSON <nickthompson@agere.com> Agere Systems
>From the windows machine I have tried NET USE \\192.168.1.22\tmp and NETVIEW 192.168.1.22 with the same result wihch leaves very perplexed. I have tried pinging the samba machine. I can ping the adress with success but pinging the name (Linux) does not work. Addind the line wins support = yes to smb.conf does not change anything. Marc -----Original Message----- From: Jason Balicki [mailto:kodak@frontierhomemortgage.com] Sent: Friday, October 24, 2003 9:55 AM To: 'Marc Drouin' Subject: RE: [Samba] Network path not found You have a name resolution error (obviously). First, try accessing the share from the Windows machines using the ip, ex: \\192.168.1.34\sharename and see if that works (dollars to doughnuts it does...) A resolution (but not the only one) would be to turn on wins serving in your smb.conf, and then point your windows workstations to your Samba server to get wins information. Alternately, if you already have a wins server on the network, point your Linux box at it. Add: wins support = yes to your smb.conf to turn on the Samba wins server. Brodcast resolution (which you're using now) should be working, however, regardless of the status of wins, unless you've entered a wins server in the clients and don't have it on on the server. HTH, --J(K)
Yes, both services are running. When I added wins supprot = yes to smb.conf, two process were created. Marc -----Original Message----- From: samba-bounces+marc.drouin=fondex.ca@lists.samba.org [mailto:samba-bounces+marc.drouin=fondex.ca@lists.samba.org]On Behalf Of Nick THOMPSON Sent: Friday, October 24, 2003 10:02 AM To: samba@lists.samba.org Subject: Re: [Samba] Network path not found Are you running both smbd and nmbd? nmbd handles the netbios queries. On Fri, 2003-10-24 at 14:33, Marc Drouin wrote:> Hi group > > I have been toying with samaba for a while now and I only manage to get it > to work haphasardly. > > The problem I have is I cannot see the shares i have created on the Samba > machine, I get a Network path not found message. > > Here is what I have so far: > > 1. Samba installed and running. Share have been created. Samba macchine > is named Linux > > 2. On the samba machine, smbclient -L Linux returns the shares I have > created. > > 3. However, the command net view Linux or net use \\linux\tmp on anyother> win machine returns "network path not found". > > 4. Also, the command nmblookup Linux on the samba machine returns > "name_query has not found name Linux" but nmblookup Winmachine retrunsthe> IP of that machine.-- Nick THOMPSON <nickthompson@agere.com> Agere Systems -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Yep! -----Original Message----- From: Jason Balicki [mailto:kodak@frontierhomemortgage.com] Sent: Friday, October 24, 2003 11:23 AM To: 'Marc Drouin' Subject: RE: [Samba] Network path not found>Addind the line wins support = yes to smb.conf does not change anything.Just so I'm clear, you did add the wins server to the tcp/ip properties on the windows client machine, right? --J(K)
Hi group, I managed to resolve my problem. It appears (newbie mistake) that during the installation of red hat 9.0 I left the setting for the firewall to medium security, in effect blocking port 137 (or 139, can't remember which). During my nmblookup test, the packet sent to port 137 por 139 was blocked. I was able to see that using the debug param of nmblookup. Anyways thanks everybody for your help. Marc -----Original Message----- From: Jason Balicki [mailto:kodak@frontierhomemortgage.com] Sent: Friday, October 24, 2003 11:23 AM To: 'Marc Drouin' Subject: RE: [Samba] Network path not found>Addind the line wins support = yes to smb.conf does not change anything.Just so I'm clear, you did add the wins server to the tcp/ip properties on the windows client machine, right? --J(K)
OK, I need help!!!! First, I've set up about 30 Samba servers over the last five years. I'm working on Mandrake 9.1. I keep getting "Network path not found" from my Windows 2000 workstation when trying to connect to my Samba server and can't understand why. I can ping the IP adddress 10.7.5.5, but when I try to find \\10.7.5.5, I get Network path not found. I turned up the logging to 10 and nothing but routine messages show up in the log. I ran testparm and it looks fine. I don't know where else to look. Any suggestions? Attached is the output from testparm. Load smb config files from /etc/samba/smb.conf Processing section "[WebData]" Loaded services file OK. Press enter to see a dump of your service definitions # Global parameters [global] coding system = client code page = 850 code page directory = /var/lib/samba/codepages workgroup = WEBSTAFF netbios name = netbios aliases = netbios scope = server string = forerunnerintl.org web server interfaces = bind interfaces only = No security = USER encrypt passwords = Yes update encrypted = No allow trusted domains = Yes hosts equiv = min passwd length = 5 map to guest = Bad User null passwords = No obey pam restrictions = No password server = smb passwd file = /etc/samba/smbpasswd root directory = pam password change = No passwd program = /usr/bin/passwd passwd chat = *new*password* %n\n *new*password* %n\n *changed* passwd chat debug = No username map = password level = 0 username level = 0 unix password sync = No restrict anonymous = No lanman auth = Yes use rhosts = No admin log = No log level = 10 syslog = 1 syslog only = No log file = /var/log/samba/log.%m max log size = 50 timestamp logs = Yes debug hires timestamp = No debug pid = No debug uid = No protocol = NT1 large readwrite = Yes max protocol = NT1 min protocol = CORE read bmpx = No read raw = Yes write raw = Yes nt smb support = Yes nt pipe support = Yes nt status support = Yes announce version = 4.9 announce as = NT max mux = 50 max xmit = 16644 name resolve order = lmhosts host wins bcast max ttl = 259200 max wins ttl = 518400 min wins ttl = 21600 time server = No unix extensions = No change notify timeout = 60 deadtime = 0 getwd cache = Yes keepalive = 300 lpq cache time = 10 max smbd processes = 0 max disk size = 0 max open files = 10000 name cache timeout = 660 read size = 16384 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 stat cache size = 50 use mmap = Yes total print jobs = 0 load printers = Yes printcap name = /etc/printcap disable spoolss = No enumports command = addprinter command = deleteprinter command = show add printer wizard = Yes os2 driver map = strip dot = No mangling method = hash character set = mangled stack = 50 stat cache = Yes domain admin group = domain guest group = machine password timeout = 604800 add user script = delete user script = logon script = logon path = \\%N\%U\profile logon drive = logon home = \\%N\%U domain logons = No os level = 20 lm announce = Auto lm interval = 60 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 = kernel oplocks = Yes lock spin count = 3 lock spin time = 10 oplock break wait time = 0 add share command = change share command = delete share command = config file = preload = lock dir = /var/cache/samba pid directory = /var/run/samba utmp directory = wtmp directory = utmp = No default service = message command = dfree command = valid chars = remote announce = remote browse sync = socket address = 0.0.0.0 homedir map = auto.home time offset = 0 NIS homedir = No source environment = panic action = hide local users = No host msdfs = No winbind uid = winbind gid = template homedir = /home/%D/%U template shell = /bin/false winbind separator = \ winbind cache time = 15 winbind enum users = Yes winbind enum groups = Yes winbind use default domain = No comment = path = alternate permissions = No username = guest account = nobody invalid users = valid users = admin users = read list = write list = printer admin = force user = force group = read only = Yes create mask = 0744 force create mode = 00 security mask = 0777 force security mode = 00 directory mask = 0755 force directory mode = 00 directory security mask = 0777 force directory security mode = 00 force unknown acl user = 00 inherit permissions = No inherit acls = No guest only = No guest ok = No only user = No hosts allow = hosts deny = status = Yes nt acl support = Yes profile acls = No block size = 1024 max connections = 0 min print space = 0 strict allocate = No strict sync = No sync always = No use sendfile = No write cache size = 0 max print jobs = 1000 printable = No postscript = No printing = bsd print command = lpr -r -P%p %s lpq command = lpq -P%p lprm command = lprm -P%p %j lppause command = lpresume command = queuepause command = queueresume command = printer name = use client driver = No default devmode = No printer driver = printer driver file = /etc/samba/printers.def printer driver location = default case = lower case sensitive = No preserve case = Yes short preserve case = Yes mangle case = No mangling char = ~ hide dot files = Yes hide unreadable = No delete veto files = No veto files = hide files = veto oplock files = map system = No map hidden = No map archive = Yes mangled names = Yes mangled map = browseable = Yes blocking locks = Yes csc policy = manual fake oplocks = No locking = Yes oplocks = Yes level2 oplocks = Yes oplock contention limit = 2 posix locking = Yes strict locking = No share modes = Yes copy = include = exec = preexec close = No postexec = root preexec = root preexec close = No root postexec = available = Yes volume = fstype = NTFS set directory = No wide links = Yes follow symlinks = Yes dont descend = magic script = magic output = delete readonly = No dos filemode = No dos filetimes = No dos filetime resolution = No fake directory create times = No vfs object = vfs options = msdfs root = No [WebData] comment = Forerunner web site data path = /usr/src/WebData read only = No guest ok = Yes