can't mount windows shares; need help interpreting log

soren625 · 09-29-2004, 04:34 PM

I used to be able to mount my Windows shares to my FC2 system with ease. Now, for apparently no reason, (although I was messing with my router configuration a bit--I think it's all as it was to begin with now), when I try to mount up one of the shares, I get :

Code:

Error connecting to 192.168.0.102 (Connection refused)
9774: Connection to 192.168.0.102 failed
SMB connection failed

I checked in the /var/log/samba and found a log called smbmount.log here is what it says:

Code:

tdb(/var/cache/samba/gencache.tdb): tdb_lock failed on list 99 ltype=1 (Bad file descriptor)
[2004/09/17 14:47:52, 0] client/smbmount.c:do_connection(156)
  1768: Connection to iliad failed

Any help would be much appreciated.

soren625 · 09-30-2004, 09:03 PM

I checked my Windows firewall settings (Windows 2000 w/ McAfee Firewall) I made sure the SMB ports were open (139, 445) I also made sure my router is allowing these ports to be open on the LAN side.

Also, now the error in the terminal is this:

Code:

timeout connecting to 192.168.0.102:445
timeout connecting to 192.168.0.102:139
Error connecting to 192.168.0.102 (Operation already in progress)
6189: Connection to iliad failed
SMB connection failed

I have no other network-related problems with either computer, (BTW, the Win2K box connects to the FC2 shares just fine). Both are fine on the 'net, and each can ping the other.

I'm very perplexed. Please help.

Sutekh · 10-01-2004, 03:45 AM

Quote:

Originally posted by soren625

I checked my Windows firewall settings (Windows 2000 w/ McAfee Firewall) I made sure the SMB ports were open (139, 445) I also made sure my router is allowing these ports to be open on the LAN side.

not sure if it is any help but you may need to have 137, 135 and 138 open - to be honest I hav enever shut these down so it may not make any difference. Is there any reason to run the firewall on the windows box?

Quote:

I have no other network-related problems with either computer, (BTW, the Win2K box connects to the FC2 shares just fine). Both are fine on the 'net, and each can ping the other.

I'm very perplexed. Please help.

so you have a win 2k box, what is the other one? win xp? if so I would still be checking (or disabling) the win firewall - seems that it works well but maybe a little too well in this case. Of cource this all assume you are running a firewall on your linux box, and the linux box is a firewall. If it isn't - that is it's just another local client, then the original question stands, do you need to firewall this box?

soren625 · 10-01-2004, 06:18 AM

I have a total of four computers on my network: 1 running Fedora Core 2 (with no iptables, or any other firewall), 1 running Windows 2000 Pro with McAfee Internet Security Suite 6 (includes Firewall), and two running Windows 98SE. All of them are connected to a D-Link wireless router (which includes a firewall.)

Sutekh · 10-01-2004, 07:46 AM

ok so the win2k box works but the 98 boxen don't? and that would make 192.168.0.102 one of the win 98 boxes?

either way maybe the best bet to start with is to step up the log level in samba to maybe 3 to get some more detail. I guess all the usual things should be checked as well, there are about a million posts here about things to look for in your smb.conf so I wont rehash them all, and I guess if the win2k box is working then it is probably ok so maybe the extra verbosity on the logs will give us a tip

soren625 · 10-01-2004, 02:11 PM

Thanks for the tip on the detail level in the log.

Just to clarify:
I am attempting to mount Windows 2000 shares, the Win98 boxes have no shares. The Win2k can access the Samba shares on the Linux box, but the Linux can't access the Win2k shares (that's what gives me the above errors.)

Sutekh · 10-01-2004, 07:05 PM

ahh ok sorry i was getting it all mixed up.

hopefully the log levels will be of more help :-)

it would probably pay to use smbclient to connect to start with that way you can change the log level in that without having to worry about smbd itself. you may need to go higher than 3 to find the answer and that generates a lot of info in your logs

if it works with smbclient then it should work with mount