Need help with samba!

[Electrode]

Hey all. Up until a few days ago, I was able to connect to samba shares on my Linux server just fine from both linux and windows clients. Now, for reasons I can't even begin to guess, I can't. Linux clients still work fine, but if I try to connect from a Windows client, I get this error:

"The network path \\supernova\hdb could not be found."

That is the only information I have. I haven't tried anything to fix it, other than restarting smbd -D about a million times, because I don't know ANYTHING about what the cause could be. I have tried connecting from different windows systems (using vmware), but they don't work either.

Specs of server:
CPU: P3 800 @ 895
RAM: 512 MB
Storage: Two 80 GB hard drives
Hostname: supernova
Distro: Mandrake 8.0
Shares defined in smb.conf: hdb, web

Specs of windows client:
CPU: P3 866 @ 1105
RAM: 512 MB
Storage: One 30 GB hard drive
Hostname: collective
Win Version: Windows 2000 Pro

 

[Nothinman]

Check the logs, usually in /var/log/samba

 

[Electrode]

no errors in the log. the last log entry is dated January 31, 2002. Now that I think of it, that was the last time I rebooted the server. Hmm...

On another note, it looks like there are a lot of connection attempts that didn't originate from a computer on my network. They all say access was denied to user "default". Hack attempts?

 

[Nothinman]

If the samba server is on a firewall/router read the smb.conf man page entries for 'interfaces' and 'bind interfaces only' and have it only listen on the loopback (127.0.0.1) and the internal network.

also turn up the log level to something like 2 or 3, you can go higher but it gets hairy if you don't understand the SMB protocol.

 

[Electrode]

It's running at loglevel 3, but it's still not telling me anything other than that it's running. It gives no indication whatsoever that conection attempts are being made.

 

[Electrode]

Hmm, just as mysteriously as it stopped working, it seems to be working again. I was trying to connect and on what I think was my 6th try, it worked. It might have something to do with the fact that I used "192.168.0.1" instead of "supernova".