FreeBSD connectivity problems on a Win98se and Win2k Pro mach
nkelly at tarsus.co.uk
Sun Oct 7 12:23:03 GMT 2001
Just a little tip with 'net use' - replace the drive letter you wish to map
to with an '*'. Windoze will replace the asterisk with the first free drive
letter - eg:
net use * \\sambamachine\tmp
From: Bill Moran [mailto:wmoran at iowna.com]
Sent: 07 October 2001 15:27
To: Unix Rookie
Cc: samba at lists.samba.org
Subject: Re: FreeBSD connectivity problems on a Win98se and Win2k Pro
Unix Rookie wrote:
> Now I seem to be able to connect to Samba from the FreeBSD box (internally
> guess) but i'm unable to connect to the samba server from my Win98se and
> machines (when I type \\(hostname) under start--->run).
You can't start->run \\(hostname). Go to a command prompt and enter
"net use q: \\(hostname)\(sharename)" (assuming that q: isn't already
mapped somewhere else.)
I've had problems with Samba showing up on W2K browsing myself. Once I've
figured out what's wrong, I'll post the solution. But I've always been able
to map drives.
> This is what I've done so far:
> 1. run both "smbd -D" and "nmbd -D"
> 2. enabled both netbios-ssn and netbios-ns in my inetd.conf file
Did you install Samba from the FreeBSD ports? If so, it creates a startup
and you shouldn't be running smbd/nmbd from inetd. It's probably not a
idea to do that way anyway. The end result is that you need to pick one
or the other (inetd/startup script) if you do both, there'll be problems.
"ps -ax | grep smbd" If you have an smbd already running, then it was
started from a startup script and you shouldn't have it in inetd.conf.
> 3. diabled my software firewalls on both my msft machines
> 4. activated sharing on both msft machines
The windows machines don't have to have sharing enabled.
"Where's the robot to pat you on the back?"
To unsubscribe from this list go to the following URL and read the
More information about the samba