"Path not accessible" from NT but not W95
kalele at veritas.com
Tue Oct 26 22:54:30 GMT 1999
The problem appears to be IP resolution, which means your WINS setup has problems. Check if your smb.conf file on the samba box has a : wins server=ip.address.of.wins.server line. And then restart nmbd. Does nmblookup from subnet C for the PDC work?
kalele at veritas dot com
----- Original Message -----
From: Shannon Kelman
To: Multiple recipients of list SAMBA-NTDOM
Sent: Tuesday, October 26, 1999 3:35 PM
Subject: "Path not accessible" from NT but not W95
a.. I have a SAMBA server on subnet A, the PDC and WINS on subnet B, clients on subnet C.
b.. SAMBA server is configured for remote announce to the PDC on subnet B
c.. nmblookup of the SAMBA server from subnet A resolves but nmblookup from subnet C does not
d.. all clients (W95, NT, and UNIX) on subnet C can see the SAMBA server (via network neighborhood for W95 and NT, ping for UNIX)
e.. W95 clients can access the SAMBA server by double clicking the server in the network neighborhood or entering the UNC in the run box
f.. NT clients receive "Path not Accessible" when double clicking the SAMBA server in the network neighborhood or using the UNC path
g.. NT clients can access SAMBA by using \\IP address\sharename
My thought is that the NT clients are failing because they require an authenticated RPC channel to communicate. However, my attempts to join the domain (yes, I followed the directions) have failed and I cannot test this assumption. I am using Samba 2.0.5a on Solaris 2.6. Any suggestions would be appreciated.
IIS Admin, Alcatel USA
-------------- next part --------------
HTML attachment scrubbed and removed
More information about the samba-ntdom