Windows Forum

Ask something
Discussion Locked

Windows, Red Hat and Samba Problem

0 helpful
9 replies

by bikergeek

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Sometimes, when we try to access our RH6.2 box which is running Samba, we get a message stating the server is not accessible - No permission to access resource. This is a winders error. You can still see the Samba mount in Network Neighborhood. To remedy this, we have to do one or both of the following: 1. Reboot the winders machine. 2. Restart Samba. I am not sure if this is a Samba config issue or a winders networking issue. Any ideas? Thanks!

9 replies

by don_p

I am using RH6.0 and samba to share some file s to winNT and 95/98. The only time I see the No Permission error is when the person logged into win does not have any permisions on the Linux box and the Guest user is not set up. It could also be thatthe win boxes are sending encripted passwords and samba is expecting plain text.

Because Win see's the samba mount I think the problem is on the linux/samba side.

You did not mention if the reboots helped. If they did you may have a differentproblem.

Hope this helps.

by bikergeek

Don - thanks for your reply. First, the win user does have permissions, and yes, the guest user is set up. I re-triple-checked the passwords issue - encrypted on both sides. As for the reboots - sometimes. When this error pops up, Winders 'loses' the rest of the network - I can still see the samba mount in the Network Neighborhood, and that is it. But I CAN still ping and telnet other machines on the network. Sometimes only restarting smb does the trick, other times only rebooting the winders box does the trick, other times both does the trick. This is happening to all win boxes trying to get into the samba mount. I'm pretty stumped!

by mckaytech

What version of Samba are you running? I had some similar problems with earlier versions of Samba but haven't seen them since upgrading to 2.0.7.

Also, just kind of thinking out loud, I wonder if there are browser wars going on between the Sambabox and your Windows network. Normally, I wouldn't expect a logon failure error message to cause the browsing in Network Neighborhood to choke.

My general sense is that it is probably a configuration issue or bug on the Samba side.
I'd be glad to take a look at your smb.conf if you would like.

paul

by bikergeek

Paul:
I'm running 2.0.6.
The Linux box is the master browser.
I will send you the smb.conf offline.
Thanks!

by dave.prosen

Check your smb.conf to see if the following line is set up (I had the same problem until I added this line) remote browse sync = x.x.x.x (subnet address). If that is not it, is the samba service set to start at bootup?

by bikergeek

I tried the remote browse sync, to no avail. And yes, the samba service does start at startup.

by bikergeek

The samba computer is also our email server and web proxy server. I can telnet into it all day with no problems. Thanks for the idea, though.

This discussion is closed to new replies.