can't SAMBA now that Linux has a domain name

[pcarver]

First, I had SAMBA totally working and the world was a beautiful place.

This morning I when into netcfg on RH 7.1 and entered a domain name. Now when trying to map the Linux shares from my Win2000 computer, it keeps complaining that the share can't be found...it doesn't show up in network neighborhood anymore either.

I suspect that it has something to do with my Win2000 domain is X, the Linux domain is Y. My smb.conf has "workroup = X". The domain on Linux, before this was blank (in netcfg).

Anyone have an idea? I really need to keep Linux and Win2000 on different domains.

/paul

 

[marsd]

YOu have different domains, win2000 pdc on one, and linux
the pdc on another is this correct?
Or you have different workgroups?
Send your smb.conf if you can.

 

[pcarver]

Again, everything was fine before. I've been accessing my Linux files from Win2000 without problem. Win2000 is in a company domain (not workgroup) that I work for, call it DOMAINX. The Linux box has a domain of Y (I filled in the "domain" text field when I ran netcfg on RH 7.1). As you can see from my smb.conf file, the workgroup field is still set to DOMAINX...I didn't think it had to be changed. I don't even see the "Samba" netbios name anymore in Windows Network Explorer. I use to access the "home" share below.

[global]
workgroup = DOMAINX
netbios name = Samba
server string = Samba Server
hosts allow = 192.168.0.
printcap name = /etc/printcap
load printers = yes
printing = lprng
log file = /var/log/samba/%m.log
max log size = 0
security = user
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd
ssl CA certFile = /usr/share/ssl/certs/ca-bundle.crt
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
dns proxy = no

[homes]
comment = Home Directories
browseable = no
writable = yes

 

[ifincham]

Hi,

The domain name in netcfg is a domain in the ip sense whereas the domains used in the samba / nt sense are netbios domains. A winbox should find a samba server by looking for the netbiosname, i.e. in your case 'samba'. Because samba only uses netbios over tcp (nbt) that needs to be resolved to an ip address. Its a bit like dns - You should be able to do 'net view \\192.168.0.1' (i.e. using ip address) without resolution as long as the routing works. However, to do 'net view \\samba' needs resolution of that netbiosname.

With samba 2.0.x, netbiosname resolution is handled by the nmbd daemon which is an implementation of a wins server. You need to put 'wins support = Yes' in your smb.conf. The default is to respond to queries for the (tcp/ip) hostname but this should be overridden when you set 'netbios name = Samba' in smb.conf . You could try running it manually with the '-n' parm to see if that makes a difference :

killall nmbd
nmbd -D -n Samba

To test resolution via nmbd :

nmblookup -U localhost -R 'Samba'

See -->

http://us6.samba.org/samba/docs/Samba-HOWTO-Collection.html#AEN309

.

Hope this helps..