Samba 2.0.7

MCCALL,DON (HP-USA,ex1) don_mccall at hp.com
Tue May 8 21:53:54 GMT 2001


Hi Richard,
In your case, the best thing would be to set your log level = 10
and specify your log file = /whateverdirectoryyourlogfileslivein/log.%m
Then try to connect via the win95 box, and take a look at the resulting
log.<win95machinename> that gets generated.  Usually you can grep on 'error'
or 'fail' and narrow down where the connection is failing and get some clue.
If you can't, send me the smb.conf file and the log file and I'll take a 
brief look at it to see if I can spot anything.
In addition include the ip address of the server and the client involved.

Hope this helps,
Don
 "Reason, not volume, is the primary
differentiator between a discussion, and an
argument."

-----Original Message-----
From: Richard Ibbotson [mailto:richard at sheflug.co.uk]
Sent: Tuesday, May 08, 2001 3:44 PM
To: samba at lists.samba.org
Subject: Samba 2.0.7


Hello

I've been helping a friend to plug a Win95 machine into a Samba 
server that I've built for him.  He's also got a Win 98 machine but 
we'll leave that out of it just now.  I've finished it and it works 
fine.  SuSE 7.1.  Using Komba2 in KDE 2.1.1 I can see the whole 
network through the Linux box.  All I have to do is click on the 
right machine in the Komba2 window and it does an SMB mount straight 
away.

However, when I try to mount the files on the Linux box from the Win 
95 machine with Network Neighborhood I find that an error message 
pops up which says that the Linux server cannot be found.  But, we 
can see the machine on the network in Network Neighborhood.

Spoke to Jeremy Allison about this and he said that he thought that 
it was something to do with the IPX protocol being enabled over the 
network.  I've removed that and I still can't get the Win 95 box to 
connect to the Linux box. He also said to try Samba 2.2 but that 
doesn't work either.

I've used all of Andrews tests which can be viewed at.......

http://www.sheflug.co.uk/networks.htm

and I've found not much that makes any sense.  All I can say is that 
it looks as though the Linux box is working fine.  'testparm 
smb.conf' reveals that all is well.  'smbclient -L BIGSERVER' reveals 
that there is an "error connecting to BIGSERVER". Don't know why. 
nmbdlookup -d 2 '*"  reveals that all is well.  'smbclient 
'\\BIGSERVER\TMP' "  shows that the connection is refused.  After 
trying to put "net view \\BIGSERVER" into a DOS window on the Win 
4.00.950 C system an error message came back which said... " Error 
53: The computer name specified in the network path cannot be 
located." Also tried "net use x: \\BIGSERVER\TMP".  It says "net: 
command not found".

Anyone suggest what I'm doing wrong here ?  Network cards are fine.  
Tried everything that I can think of.

Thanks

-- 
Richard

http://www.sheflug.co.uk

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba




More information about the samba mailing list