9 replies
Try to make the following changes in smb.conf:
security = user
domain logons = yes
os level = 34
By the way, I reccomend you do not use SWAT and make all the changes manually. Besides, there is a good book "Using Samba" which is free and distributed with new SAMBA packages. There is a lot cool information about servers setup.
by iftequar
by d'anno
by iftequar
by brianaaa12
Unless newer versions os Samba have changed, you need to install NetBEUI AND TCP/IP on the client workstations. Samba uses both.
Try telnetting to the Linux box. If it lets you in, then you will at least know that your TCP/IP and username and password are working properly.
brian
by iftequar
Ok, I've had this same issue.
go to the /etc directory. type pico smb.conf
go to the [global] section
look and see if there is a setting that looks like this
workgroup = *SOMETHING*
if there is anything typed there, replace it with your internal domain and or workgroup.
then, save the changes to smb.conf, exit pico, and type testparm
that will restart your samba service.
hit refresh in network neighborhood and it should be there.
by iftequar
by iftequar
This discussion is closed to new replies.
Trending Linux posts
Sort by Trending