Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!chi-news.cic.net!newsfeed.internetmci.com!news.mathworks.com!udel!stimpy.eecis.udel.edu!alexandr
From: alexandr@stimpy.eecis.udel.edu (Jerry Alexandratos)
Newsgroups: comp.protocols.smb,comp.unix.bsd.freebsd.misc
Subject: Re: Samba and PC/TCP?
Date: 19 Dec 1995 21:55:33 GMT
Organization: Mos Eisley Candy Store
Lines: 77
Message-ID: <4b7ccl$7tc@louie.udel.edu>
References: <4b4n3l$d71@louie.udel.edu> <4b73kl$fjl@news.rrz.uni-koeln.de>
NNTP-Posting-Host: stimpy1.eecis.udel.edu
Xref: euryale.cc.adfa.oz.au comp.protocols.smb:3268 comp.unix.bsd.freebsd.misc:11196
In article <4b73kl$fjl@news.rrz.uni-koeln.de>,
Stefan Esser <se@ZPR.Uni-Koeln.DE> wrote:
:In article <4b4n3l$d71@louie.udel.edu>, alexandr@stimpy.eecis.udel.edu (Jerry Alexandratos) writes:
:|> I'm trying to connect a few machines runnign WfWG to a FreeBSD box
:Well, it is working! At least for me ...
I've got the server working just fine.
:|> The pc's are running WfWG v3.11 and are using PC/TCP v3.11 as for
:|> their tcp stack. Likewise, these machines are logged onto a Novell
:|> v3.11 server.
:Did you enable the TCP/IP protocoll stack
:in the WfW network setup ?
Yes, the protocol stack is enabled. Every other PC/TCP application
works just fine. My guess is that something in the netbios support
for windows isn't working correctly, or doesn't allow it to see the
other workgroups (more on why in a second).
:What's your value of LASTDRIVE ?
Z, as it should be for NetWare v4.x clients (ie VLM's).
:It is!
:
:Well, as long as you don't send any detailed
:error log information (you did enable debugging
:using some reasonable value, say 3, didn't you ?)
:we can hardly offer any advice ...
I do apologize for this, I didn't know what error stuff to include.
Let me give you a quick rundown of what I can and can't do.
From the FreeBSD box, I can connect to the Samba server (on said box).
From the MS-DOS box, I can connect to the Samba server after I load up
the PC/TCP protocol stack and netbios driver using the DOS 'net'
program (eg net use i: \\hawk\service).
From WfWG, not a damn thing. Not only that, but it also fails to
recognize the MS-DOG box as well.
If I run 'net start full' on the pc's and then start WfWG, I can then
map the samba server, but I can't recognize any of the other plain
WfWG boxes, I get an error saying that I'm out of NetBIOS connections.
My guess is that this problem probably has something to do with
netbios/netbeui talking to one another.
And finally, I can't use smbclient. I try to connect to a machine
using the following command :
'smbclient '\\robin' -I robin.pearson.udel.edu'
I get the following returned:
12/19/95 16:50:48 client started (version 1.9.15p6)
Opening sockets
Connecting to 128.175.64.107 at port 139
Connected
Sent session request
Session request failed (131,130) with myname=HAWK destname=ROBIN
Called name not present
Try to connect to another name (instead of ROBIN)
You may find the -I option useful for this
I get the same results when I use P7 which is the machine's WfWG name
(speaking of which, how can I change the samba server's name from
something other than it's hostname? I thought it was just 'nmbd -n
NAME', but putting that in my inetd.conf doesn't do anything. Can
this be specified in the smb.conf file?)
Sorry for the length of this post, I hope someone out there can help
me out. Thanks in advance...
--Jerry
--
8) Jerry Alexandratos % - % "Nothing inhabits my (8
8) alexandr@louie.udel.edu % - % thoughts, and oblivion (8
8) darkstar@strauss.udel.edu % - % drives my desires." (8