[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Samba and 2k



I'm running Samba 2.2 under Debain unstable as a PDC.  I
have a Win98 machine logging into the PDC just fine.  I can
also see the Linux box in Network Neighborhood and access
the shares.  I have a second machine on the same network
running Win2k.  The Win2k machine does not see the Linux box
in Network Neighborhood.  Attempts to map a network drive by
specifying a full path fail.  So does trying to access
//Name or //a.b.c.d in My Computer.  Attempts to have 2k log
into a domain fail with the error that the controller can
not be found.

I can, however, ping the Linux box from 2k, using either IP
address or computer name.  I can access it via ftp, ssh and
VNC.

I have the Linux IP entered as a WINS and DNS server on the
2k machine.  Looking in log.nmbd, I see lots of messages
with the 98 machine IP.  The 2k machine IP does not appear
at all.

I'm running out of things to fiddle with and having no luck
what so ever.  98 and Samba are cozy as can be.  2k and 98
talk just fine over NetBIOS.  2k and Linux talk fine over
non-NetBIOS channels but 2k and Samba refuse to even look at
each other.

From my smb.conf file:

[global]
security = user
status = yes
encrypt passwords = yes
guest account = nobody
share modes = no
os level = 65
keep alive = 30
kernel oplocks = false
socket options = TCP_NODELAY
map to guest = Bad User
logon script = %U.bat
logon path = \\%N\%U\profile
;
workgroup = amber
domain logons = yes
domain admin group = admin
domain master = yes
preferred master = yes
;
admin users = root
map hidden = yes
map archive = yes
map system = yes
;
browseable = yes
write raw = yes
read raw = yes
oplocks = yes



Ideas or suggestions, no matter how wild, gladly accepted.



Reply to: