samba problems... please help

[xyyz]

I've had enough of Samba... I can't get the damn thing to work... no matter what I try!!!!!!!!

I installed Samaba from the sources on my FreeBSD 4.4 machine.

I made a simple smb.conf file. I manually ran smbd and nmbd with the "-D" argument. I can use smbclient to connect internally from my FreeBSD box. In addition, testparm, yields no errors.

But... for the life of me I cannot get my useless windows machines to connect to the samba server. I've tried it all... i've tried mapping the drives... using "net use e: \\froggie5\test" and "net view" from the dos prompt.

I can't get through to friggin Samba...

ports 137-139 are in my /etc/services file.

I can connect to SWAT from my windows machine...

But... I cannot my windows machines to see my FreeBSD box on the LAN.

This is really annoying me.

All help would be really appreciated.

 

[ttn1]

What windows are you using. If win2000 or winNT you need to activate encrypted passwords in the smb.conf file. Or you could enable plain text authentication on the win2K/WinNT boxes.

You also have to have accounts on the BSD box with samba passwords. If you use win9x machines the passwords have to match, because win9X doesn't let you connect to samba using a different password.

I fought with this for about 3 months before I got it working, so I feel your pain. Once it's working though it is great. I read probably 300-400 pages of howtos and FAQs.

ttn1

 

[xyyz]

<< What windows are you using. If win2000 or winNT you need to activate encrypted passwords in the smb.conf file. Or you could enable plain text authentication on the win2K/WinNT boxes. >>



Win98se and Win2kPro... have the encrypted passwords enabled in the smb.conf file.



<< You also have to have accounts on the BSD box with samba passwords. If you use win9x machines the passwords have to match, because win9X doesn't let you connect to samba using a different password. >>



Done... although i'm not even to this point... because the windows machines cannot detect the FreeBSD machine on the network.

 

[ttn1]

Here is one other thing to try type smbclient -L localhost on the BSD machine. This should show your active shares.

Samba HowTo

This is a good samba howto if you haven't already read through it. If the share shows up as active on the BSD machine, then you should be able to connect using net use or map network drive from right clicking on the my computer icon.

Don't worry about windows not seeing your machine. I have two samba machines here at work and 2 at home and my windows machines hardly ever show them. If you can ping the BSD machine then windows can "see" it. Don't worry about what the evil network neighborhood says. That thing is from the devil.

If passwords are correct the only other thing it could be is the samba port. Grab AutoNOC and install it on the win2K machine. Scan the BSD machine to make sure the right port is open. The scanner is great for checking to see which ports are open on a machine. I used it extensively when I upgraded to Redhat 7.1. Damn firewall/ipchains. Took me a week to iron all that out.

Good Luck.

ttn1

 

[xyyz]

this is what I get with the "smbclient -L localhost"

Anonymous login successful
Domain=[HOME] OS=[Unix] Server=[Samba 2.2.2]

Sharename Type Comment
--------- ---- -------
test Disk For testing only, please
public Disk publicly accessible
IPC$ IPC IPC Service (Samba 2.2.2)
ADMIN$ Disk IPC Service (Samba 2.2.2)

Server Comment
--------- -------
FROGGIE5 Samba 2.2.2

Workgroup Master
--------- -------
HOME FROGGIE5

See... the thing is I can't even connect to the FreeBSD machine from the Win machines... that's where all the frustration lies.