Windows to Samba, Network path not found

LoRd Of XAoS · 03-26-2005, 07:21 PM

Greetings all!

I've been surfing around the forum for a while and have done mass amounts off googling, but STILL can't find an answer to my problem.
Hopefully you l33t people can help me out.

I'm running a FC2 server on my network.
It has an ftp server, http server, etc...
I can ping the server and it can ping anything else... not a problem.

The rest of the network is varing degrees of windows. mainly XP and Win2k.

So this is my problem -

I would really like to access files / print on the linux box from the windows machines on the network preferably through samba (I can already FTP/SSH in without a problem).
I have samba set up and configured (I think correctly, but obviously not because I have this problem), and CAN mount any share on any windows machine just fine.
The problem comes in when I try to access a share on the linux machine.

If I view the workgroup from a windows machine, the linux box shows up just fine. However when I try to access the box I get this message:
"\\LINUXBOX is not accessible. You might not have permission to use this network resource. blah blah...
The network path was not found"

I belive that I have correctly set up samba users and have set the permissions, but obviously I have failed somewhere.

I also don't understand, because I can access shares FROM the linux machine just fine.

Here is a copy of my smb.conf:

Code:

[global]

# workgroup = NT-Domain-Name or Workgroup-Name
	workgroup = MYWG

# Netbios Name
	netbios name = LINUXBOX

# Server sting
	server string = Linux file server

# Samba Security Setting
	security = user

#Use password encryption
        encrypt password = yes

#Set master browser setting
	username map = /etc/samba/smbusers
	password server = None
	local master = no

# ========== Share Definitions =========
# Configure local shares

[netshare]
	comment = Lan Stash Spot
	path = /usr/netshare
	guest ok = no
	writeable = yes
	printable = no
	create mask = 0765

If anyone has any ideas I would greatly appreciate the help.
After I figure this one out, I need to figure out how to get printing to work from the network as well. However i feel that will be a WHOLE other can of worms.

Thanks.

Ps. Sorry if this is a duplicate thread somewhere else on the board, have been unable to find anything similar to this problem.

cowanrl · 03-27-2005, 07:37 AM

That acts like a firewall problem. Stop your firewall temporarily and then try to access the Samba shares. If that solves your problem, you'll need to modify your firewall to allow the smb traffic in.
If you do a search on this site for "samba and firewall" or "samba and iptables", you should find some recent posts on configuring a firewall for Samba traffic.

1newbie2 · 03-27-2005, 08:23 AM

I am having the same problem but have no firewall. any other suggestions?

LoRd Of XAoS · 03-28-2005, 08:00 PM

Yeah...
I checked the firewalls, disabled them... so on and such forth...
Still nothing however....
Checked IP tables and configured it for samba traffic... still nothing...
Any other help would be awesome.

cowanrl · 03-28-2005, 08:40 PM

You'll want to make sure both smbd and nmbd are running. In FC, you should be able to execute as root:

service smb status

and it should list the status of both of those dameons.

You can also try this from the linux command line when you are logged in as one of the samba users you have created:

smbclient -L localhost

it should prompt you for a password and then display some information about your Samba server and show the shares on it.

If that works, try:

smbclient -L linuxbox

and it should do the same thing.

Post the results of those commands here.

{BBI}Nexus{BBI} · 03-28-2005, 09:24 PM

You could try adding a <valid user/s=> option.

snaib · 03-29-2005, 05:13 AM

Configuring Squid for initial use

1newbie2 · 03-31-2005, 07:33 PM

Hey,

I solved my problem .. i had followed all the steps to setup SAMBA at http://us4.samba.org/samba/docs/man/...diagnosis.html and then I rebooted my Linux box. Before rebooting it didn't work. I am guessing something had to be re-initialized in order for it to work ...

Hope this helps!