There is another thing to try. Since the share appears in the
network neighorhood, (I assume under the appropriate computer name)
you can change the debug level in the smb.conf file to 3 or 4 (or even 10)
and hit the smbd and nmbd processes with "kill -1 <thesmbdpid>
<thenmbdpid>"
and try the access again. When you scan through the log, you will see
the access from your win2k machine come in and start to get processed,
evenutually you will see the log.smbd complain about something and fail
the connection.
If you actually can just see the machine in network neighborhood but not
see the shares inside, look at the log.nmbd and see what it has to say
about the access to the machine.
The logs may provide some clue.
"Loo, Joseph" wrote:>
> Have you checked the network permission and the directory permissions.
>
> -----Original Message-----
> From: Clifford Crestodina [mailto:clifford@crestodina.com]
> Sent: Monday, January 28, 2002 6:26 AM
> To: samba@lists.samba.org
> Subject: SWAT - network path not available from WIN2K
>
> I'm missing something in setting up SAMBA via SWAT.
>
> After creating the user and the share in Linux and after running SWAT to
> publish the share I can SEE the share in Network Neighborhood but when I
> try to open it tells me that the "Network Path is Not Available".
>
> I've restarted smbd AND nmbd.
>
> I stumped.
>
> Clifford
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: http://lists.samba.org/mailman/listinfo/samba
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: http://lists.samba.org/mailman/listinfo/samba
--
Robert E. Styma
Principal Engineer
AG Communication Systems, Phoenix - A subsidiary of Lucent
Email: stymar@agcs.com
Phone: 623-582-7323
FAX: 623-581-4884
Company: http://www.agcs.com
Personal: http://www.swlink.net/~styma