FreeBSD connectivity problems on a Win98se and Win2k Pro machine

[Yves Gattegno]

Hi

The problem you have may be related to NetBIOS name resolving.
To bypass NetBIOS name resolving, under Win98se and Win2K you should 
be able to use IP address instead of hostname

For instance, try the following

C:\WINDOWS>net view \\<SambaServer IP Address>

If this works, then you have a NetBIOS name problem.
You may then need to implement some LMHOSTS or WINS-like NetBIOS
names resolving.

If the test doesn't work, try to ping the Samba Server from 
your Windows boxes.

Hope this helps

Yves




En réponse à Unix Rookie <unixrookie at yahoo.com>:

> 
> 
> Alright... i did what you and Yves suggested...
> 
> Here's the output of both commands:
> 
> C:\WINDOWS>net use q: \\froggie5\sameer
> 
> Error 53: The computer name specified in the network path cannot be
> located.
> Make sure you are specifying the computer name correctly, or try again
> later
> when the remote computer is available.
> 
> 
> C:\WINDOWS>net view \\froggie5
> 
> Error 53: The computer name specified in the network path cannot be
> located.
> Make sure you are specifying the computer name correctly, or try again
> later
> when the remote computer is available.
> 
> 
> I intially installed Samba through the FreeBSD ports... but I later
> uninstalled
> it because it was an older version (2.08)... I honestly dunno why the
> sources
> of an older version are present when I run cvsup three times a week.
> 
> I downloaded the latest Samba build and did the: 
> 
> ./configure 
> make && make install
> 
> This has given me another set of problems that are more annoyig thatn
> problematic (these files aren't included in my path even though I
> manually
> added them in both the .profile and .bash_profile files)
> 
> -Sameer
> 
> 
> 
> 
> --- Bill Moran <wmoran at iowna.com> wrote:
> > Unix Rookie wrote:
> > > Now I seem to be able to connect to Samba from the FreeBSD box
> (internally
> > I
> > > guess) but i'm unable to connect to the samba server from my Win98se
> and
> > Win2k
> > > 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
> > script
> > and you shouldn't be running smbd/nmbd from inetd.  It's probably not
> a great
> > idea to do that way anyway.  The end result is that you need to pick
> one
> > method
> > or the other (inetd/startup script) if you do both, there'll be
> problems. 
> > Type
> > "ps -ax | grep smbd"  If you have an smbd already running, then it
> was
> > probably
> > 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?"
> 
> 
> __________________________________________________
> Do You Yahoo!?
> NEW from Yahoo! GeoCities - quick and easy web site hosting, just
> $8.95/month.
> http://geocities.yahoo.com/ps/info1
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba
>