I have two computers, samson(win 2k server) and frodo(linux).

i can connect to win2k server from linux through the command line like this.

>smbclient //samson/download -U Administrator password

then i can just see the files from public directories existing in win 2k server from linux.

and even though i ping win 2k server with the local ip and computer name on linux, i get a reply from it. but when i try to ping frodo on windows 2k server, i don't get the reply. but i get the reply by pinging the local ip of the linux machine.

what i want to do is browse frodo in windows 2k server so that i can shares files and also use the server, too.

on "Computers Near Me" on win 2k server, it shows "frodo", but when i try to browse, i get "Frodo is not accessible. The network path was not found.". i don't know why i can't get access to the linux machine from windows even though i can get access to windows from linux.

here is my smb.conf
[global]
log file = /var/log/samba/%m.log
load printers = yes
smb passwd file = /etc/samba/smbpasswd
passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*
obey pam restrictions = yes
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
username map = /etc/samba/smbusers
hosts allow = 192.168.1.101 192.168.1.100
encrypt passwords = yes
wins proxy = yes
passwd program = /usr/bin/passwd %u
dns proxy = no
netbios name = frodo
browseable = yes
netbios aliases = frodo
server string = samba server
printing = cups
default = public
path = /tmp/download
unix password sync = Yes
workgroup = workgroup
os level = 20
auto services = public
printcap name = /etc/printcap
security = user
max log size = 0
pam password change = yes

[homes]
comment = Home Directories
browseable = yes
writeable = yes
valid users = %S
create mode = 0664
directory mode = 0775


[printers]
comment = All Printers
path = /var/spool/samba
browseable = no


[public]
path = /home
public = yes
only guest = yes
writable = yes
printable = no
browseable = yes

I am having the same exact problem. Know what is weird, my linux box is called frodo too.
What distribution are you running? I am running Suse 9.1.

My windows box could see my linux box until I changed my Netbios name to "frodo" and now it can't find it at all.

i am using red hat 9.

can't figure it out.. i have been stuck in this problem for 2 weeks...

Maybe its the firewall, make sure its not blocking ports Samba is using.
TCP 139, 445
UDP 137, 138
by default

how can I know my firewall block these TCP and UDP port. I've chosen disable Firewall in Security Level Configuration but still have this trouble.

Make sure samson is part of the workgroup conveniently called "workgroup". Next make sure you added the user via smbadduser? Make sure samson is in "hosts allow =" and double check you firewall as Demonbane mentioned. You may want to add samson to /etc/hosts just for ease. As for your firewall:

[somedir]# redhat-config-securitylevel

Click on "Customize".
Click the check box for your network adapter (usually "eth0").

Click on the checkboxes for any services you want to allow (I allow WWW,
FTP and SSH).

In the "Other ports" edit box, enter
"137:udp,137:tcp,138:udp,138:tcp,139:udp,139:tcp,445:tcp". At a command prompt type

[somedir]# service iptables stop
Flushing all chains: [ OK ]
Removing user defined chains: [ OK ]
Resetting built-in chains to the default ACCEPT policy: [ OK ]
[somedir]# service iptables start
Flushing all current rules and user defined chains: [ OK ]
Clearing all current rules and user defined chains: [ OK ]
Applying iptables firewall rules: [ OK ]

This should allow all the packets necessary for Samba.

{snip from "http://lists.samba.org/archive/samba-docs/2003-March/000288.html"}

More good info:

- - Your hint should only apply to a firewall that serves to harden your server
~ installation, i.e. if you use iptables on your server to control, which
~ kind of packets *from your local net* your server responds to.
~ If your firewall has the additional purpose to separate your local net
~ from the internet, then allowing NetBIOS over TCP/IP is not a good idea.
~ There are currently several windows worms that scan random IP address
~ ranges for weakly protected windows shares, so opening up your network to
~ these protocols is a bad idea!
~ To repeat that: You should open Ports 137, 138 and 139 (UDP and TCP)
~ only for your local net, not for the internet.

{snip from: "http://lists.samba.org/archive/samba-docs/2003-March/000289.html"}

yeah! thanks micxz. My share displayed.

Great glad to help. Was it the workgroup or smbadduser?

I've followed your posted,. At Samba Setting window, I leave default workgroup name is "mygroup" and add 1 samba user named ADM. Windows users can access my share now

ah, when I create Samba User, I see 2 options: Unix Username (I chose ADM - the 1st user in list) and Windows username (I typed "admin") and leave blank password.

When I move to Windows and try access my shared folder, the username and password appear, if I type "admin" (windows username), access denied. if I type ADM and enter, it work. Can you tell me why it is.

Thanks

I think this accurs because there is not linux user "admin". But there is a user ADM. Or maybe I misunderstood the question. (It's getting late)

This is the correct format for smbadduser:
smbadduser unixid:ntid

hey

4:00 in the morning and I don't know why I am awake. From your smb.conf file, it seems like you are still using samba version 2.8 , 2.9 , or something like that. I would make sure two major things.

#1 Make sure your workgroup on your W2k and smb.conf file match.
#2 Make sure you have added the IP number of the linux box in as wins server in your W2k Machine

I would do a computer search and see if you can find it. If not, you may have more problem than I can see. Since I don't see the whole configuration file, I can't really help you with from what you have. If it helps, here is my configuration file

don't forget samba -a 'username'

Sorry, I am kinda sleepy and have to get up in 3 hours for work

Ambex