Windows2000 Network Path Not Found :-\

sancho5 · 08-24-2001, 05:03 PM

same setup i have

anyways, the lack of the encryted passwords =yes line in your smb.conf would be part of the reason you weren't connecting on your first post... Win2k sends encrypted passwd files, so make sure that is set. Also, make sure the user you are connecting as from the win box has an account on the Samba server - both a regular Unix account, and a "samba" account that you have setup by running the

Code:

#smbpasswd -a <username>

That should allow you to at least connect to the server - to test it, run the following command from a DOS prompt:

Code:

net view \\<server>

where <server> is the netbios name of your samba server. If you are allowed access, it will show you a listing of the shares available on the server. Also, try pinging the server, both by IP address and by NetBIOS name.
See what you come up with.

Jase · 08-24-2001, 05:07 PM

F:\>net view \\gs2
System error 53 has occurred.

The network path was not found.

F:\>ping gs2

Pinging gs2 [192.168.1.10] with 32 bytes of data:

Reply from 192.168.1.10: bytes=32 time<10ms TTL=255
Reply from 192.168.1.10: bytes=32 time<10ms TTL=255
Reply from 192.168.1.10: bytes=32 time<10ms TTL=255
Reply from 192.168.1.10: bytes=32 time<10ms TTL=255

Ping statistics for 192.168.1.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

F:\>

Jase · 08-24-2001, 05:28 PM

well I just ran "\\192.168.1.10\ftp from the run menu and this is the error I got.

"\\192.168.1.10\ftp

The semaphore timeout period has expired."

sancho5 · 08-24-2001, 05:40 PM

Hmm... the "net view" command you ran should have showed a listing of the shares available on the server. The message it gave you tells me that you aren't allowed access to the server with the user you are trying to connect as. (Disclaimer: I *could* be wrong)
Make sure that the user name and password you are logged into windows with has an exact match on the Linux box: you can do things to make this different, but to keep it simple, make it exact matches. When you do the #smbpasswd -a <username> you can specify a different "SMB" password that matches the one from the win box.
It could also be that the NetBIOS name is not set on the linux box. Try editing the .../lmhosts file to make sure you have the address/name mapping for your linux box in there.
Another thing - when you make changes, are you restarting SAMBA?

Jase · 08-24-2001, 05:44 PM

Yes I am restarting the service. I have a question though. Is there a way I can use this as a sorta of anon ftp? I want my local LAN clients to be able to dump files (backup purposes) to this linux server like a mapped drive. Is this possible?

Jase · 08-24-2001, 05:51 PM

Sancho,...I tried making my username for smb the same as my windows client username and I have tried making my password the same as my linux and windows client. Neither work. Anything else I should try?

sancho5 · 08-24-2001, 06:10 PM

Yeah, it is possible. Samba is perfect for what you want, in that respect.

We could try to troubleshoot the setup you have now, or you could make sure the below is met for a minimum.

Assuming you have a folder on the linux box named "ftp" that you want to share thru Samba:
set the permissions to 770 on that directory, and ownership to that account you will be connecting as.

in the smb.conf, setup a section as follows:

[ftp]
path = <path on filesystem>
browseable = yes
comment = <whatever you'd like>

As for global config options, make sure the following are set:

[global]
workgroup = <your workgroup name, all caps>
netbios name = <what you want the server name to be (optional)>
security = user
hosts allow = 192.168.0. 127.0.0.1
encrypt passwords = yes
server string = <description of server (optional)>

***
I believe this should work, and then you can add additional options as you see fit. Make sure the user has been given encrypted smb passwords with #smbpasswd -a username (i said it before, but just incase) and keep in mind you may need to add the involved servers/clients addresses & names to .../samba/lmhosts.
try connecting locally with

Code:

#smbclient //localhost/ftp

and see if that allows you to connect (do this with the account on the linux box)
Also try with

Code:

#smbclient //<servername>/ftp

- this way it has to resolve the name of the server to it's IP address to connect. try the UNC (\\server\share) login again from the 2000 box, and see then.
If you are still having probs after that.. slit your wrists

just kidding. Hopefully someone else on the forum could point out the one option that we are missing.
If I haven't yet, let me refer you to http://www.oreilly.com/catalog/samba...ook/index.html - This is a cool guide.

Jase · 08-25-2001, 12:14 AM

well the smbclient does not work for some reason. If I do a locate smbclient I find nothing. So,...I have decided to cut my wrists and die slowly

LOL

Jase · 08-25-2001, 01:01 AM

well shit,....I loaded samba on my webserver,......it gave me the same error the first time I tried it,....then I set ownership of the dir to my name.group and it came up with the login prompt. But when I put my username and pass in it gave me a semaphore time out or something error. Any time I try it now,...it says that ws1 is not accessiblew Network path could not be found

Jase · 08-25-2001, 01:04 AM

well now I just ran this and got a different error,... *sigh*

Code:

F:\>net view \\ws1
System error 53 has occurred.

The network path was not found.


F:\>net view \\ws1\stuff
System error 123 has occurred.

The filename, directory name, or volume label syntax is incorrect.


F:\>net view \\192.168.1.5
System error 53 has occurred.

The network path was not found.

I am lost

Jase · 08-25-2001, 10:54 AM

well praise the Heavens, samba now runs on my LAN server

although it did give me this funny error

Code:

[10:43:35] [root@gs1:/etc/samba (.001 Mb)]# smbpasswd -a pcb
New SMB password:
Retype new SMB password:
startsmbfilepwent_internal: unable to open file /etc/samba/smbpasswd. Error was No such file or directory
Added user pcb.

It added the user and the user in the /etc/samba/passwd file. Ohh well it works

check out my smb.conf now,....LOL

Code:

[global]
        workgroup = TAELONET
        encrypt passwords = yes 
        server string = FILE BITCH
        security = user

[pub] 
        comment = For testing only, please
        path = /var/ftp/pub
        read only = no
        guest ok = yes
        comment = Get what you need and get out  :D

sancho5 · 08-25-2001, 01:03 PM

hahaha.. cool.

Looks like what you'd been missing before was the #smbpasswd -a username - it tells you this is the first one you created with that error. Now you have an SMB password setup for your user.
your smb.conf looks a lot like mine now - like one of my proffessors always said, simplify simplify simplify...

Wildfox · 08-30-2001, 08:41 AM

This post is in reguards to the 95 question.

Win 95 doesn't use encryped passwords. So you don't need to set it up on linux. You can set 98 or nt 4 to use non encrypted passwords. You would need to modify the registry for that.

I am running into the sam problem you are. (I can see the linux box. I can even see directories but can't access the directories.) The only thing that I can think of is that the user doesn't have the right permisions to access (I.E. user rights to directory) or that the encyption is causing you problems. I am no expert but this is my opinion of what might be happening. I was kinda lazy about setting up the user accounts on it and I think this may be my problem. Who knows.