Re: Samba and 2k
Just guessing here:
1. W2K has NetBIOS, but not over TCP/IP.
2. Your W2K user lacks proper permissions on the Samba side.
3. W2K security is preventing you from seeing samba. W2K security
seems distinctly tighter than NT 4, annoyingly so.
4. W2K thinks it is PDC and refuses to play with Samba.
5. Your WINS service is not running properly on Linux box. Perhaps it
refuses to respond
to requests from the W2k box because it only attends to certain IP addresses.
Each idea has an implicit theory about how things work that may be wrong
(e.g., point 1 assumes samba uses NetBIOS over TCP). It's just a list of
possibilities that might be worth exploring.
At 12:53 AM 6/16/01 -0400, Daniel Jones wrote:
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.
Ideas or suggestions, no matter how wild, gladly accepted.
Reply to: