Samba: Windows boxes can't access my FC2 Samba shares

[iontyre]

I installed and setup the samba server on my FC2 box, and have two other windows machines on my network serviced by a DLink 614+ router/switch. The windows machines show the Samba Server in the Network Neighborhood, but I get an access denied when I try to browse the server for shares. I do have a shared directory on the server. I expect this is a username/password issue. My win boxes login with a full name (Joe E. Blow) and no password. Is there something else I need to setup on the server end?

[zebra]

Have you set up your network username and password? If not, then in xp go to start/controlpanel/user accounts/choose your account/in the upper left hand corner choose manage my network password.

the format for your password is for user name type in

server/user name

server is the name of your samba server.

[iontyre]

I'm using Win98 on my win boxes. Isn't my username and password as I specified above? I don't use a password, but do have a login name.

[pawelgm]

I have all kinds of issues with SMB also but I found this works:

in the Internet Explorer type in

the ip of your linux box and the share name and wait like 10 sec and it will come up without asking for password example:

\\192.168.1.100\Stuff\

192.168.1.100 is the ip
Stuff is the directory I have shared

give it a try, when I type in \\192.168.1.100 it asks me for a password

[iontyre]

Not working at all, guys. My win98 box shows localhost in the network neighborhood, along with Samba Server in the comment column, but if I click on it I get "\\localhost is not accessable. The computer or share name could not be found. Make sure you typed it correctly, and try again. I have followed all the directions in the samba config utility, but I must have something set up wrong. If I boot my server in Win98 instead, all the other computers see it just fine, but in FC2 I can't seem to get it working right.

[engwnbie]

Did you try?
This works for others.http://www.fedoraforum.org/forum/sh...p;threadid=2556

There are also great examples and how to on your fedora installation. FC1 is a bit different. FC2 in /usr/share/doc/samba-3.0.3/docs there are pdf files that explain how to samba network with other operating systems. Samba-Guide.pdf has different examples and how to implement.

[embjet]

Make sure there is a user account on the linux box with the same username and password as the windows 98 box. Log on as root on the linux box and using the following command "smbpasswd -a" type in the username and password that the linux account from above uses. Make sure that in the "smb.conf" file there is an entry that states: "encrypt passwords = yes"


To test you install use a "smb.conf" that has about 3 lines. Keep it simple at first.

See Ya

[iontyre]

I've done all these things. None of it works. netstat -a does not even show samba running!!! Yet I have restarted samba, and it reports the restart worked OK. What the hell is going on?

[tbldusr]

netstat won't show a samba. Use ps -A and look for nmbd and smbd. If you're seeing the Samba Server from your windows machine then samba is running. From your earlier post you said that it complains about \\localhost. I had the same problem at first and it is because your fedora machine does not have the hostname set (analagous to computer name in windows - it ought to ask for one when installing but it doesn't). Open up your network configuration dialog (System Settings->Network), go to the DNS tab, and change the hostname from "localhost.localdomain" to something else like "fedora". Reboot the computer and everything should work.

[Nitro]

Have you set your samba share with a user / password?

As above make sure you change hostname from localhost to mylinux (or other name of choice) in /etc/sysconfig/network and /etc/hosts to something along the lines of 127.0.0.1 localhost.localdomain localhost mylinux (or other name of choice)

Also can you go from FC2 samba to your winboxes? I.E. is this a 1 way traffic issue, can samba acesss a share on a winbox?

[tromas]

Did you open the firewall on the FC box
(137-139, 445 tcp and udp).

[michael_salcher]

the solution can be found at http://support.microsoft.com/kb/q187228/

details (taken from the above website):
This behavior occurs because Windows 98 does not send plain text passwords to Server Message Block (SMB) servers by default.

Method 1
Configure the Samba server to support Challenge-Handshake Authentication Protocol (CHAP) password encryption. Please refer to your Samba documentation for information on how to configure a Samba SMB server.
NOTE: This is the preferred method to resolve this issue because it is more secure than sending unencrypted passwords over the network.

Method 2
You can enable Password Authentication Protocol (PAP) plain text password use in Windows 98. To do so, use the following steps.
WARNING: If you enable plain text password use in Windows 98, all passwords are sent on the network in an unencrypted format. These passwords may be viewed by anyone using a network monitoring program. If security is a concern for your network environment, do not enable plain text passwords.
1. Insert your Windows 98 CD-ROM into the CD-ROM drive.
2. Click Start, and then click Run.
3. In the Open box, type <drive>:\tools\mtsutil, where <drive> is the letter of the CD-ROM drive that contains the Windows 98 CD-ROM, and then click OK.
4. Right-click the Ptxt_on.inf file, and then click Install.
5. Restart your computer.

Method 3
You should use the following method only if you do not have access to the Windows 98 CD-ROM. These steps enable PAP password use without the CD-ROM as mentioned in method 2.
1. Start Regedit.exe.
2. Locate the following key in the registry:
HKLM\System\CurrentControlSet\Services\VxD\VNETSUP
3. Change the data value for the EnablePlainTextPassword value to 1.
4. Restart your computer.

[sosmeister]

I'm sure someone has already mentioned this, but make sure that you've opened up the ports in your Linux firewall. I had a similar problem a few weeks ago setting up Samba on a RH9 box, and silly me forgot to do this step and I had very similar symptoms. Try pinging the Linux box and see what results you get (I can't remember the specific port numbers off hand). Otherwise, it sounds like your Samba users aren't set up correctly.

If I'm wrong about something, let me know. I'm new here, and relatively new to Linux. Love the site by the way.

[jayemef]

If you're not using passwords on the windows boxes, do you even want your samba shares password protected? If not you might want to try using the force user parameter in your smb.conf file. The use of force user ensures that all files are owned by the same user identifier (UID) and thus ensures that there will never be a problem with file access due to the access permissions.