samba - Mar 1999 - Samba and Novell

WARNING   Newbie question  WARNING


	I am attempting to get Samba up and running.  It is installed on a RH5.2
box, and everything went pretty well.  I can see the samba box in Win95
network neighborhood, but I can's connect to it.  I am suspecting that the
Novell 4.1 box on our network is interfering.  I can't seem to find a good
document on samba/novell stuff, so any assistance would be greatly
appreciated (especially since I know nothing about Novell, and have gotten
permission to replace the Novell box with Samba, as soon as I get it up and
stable).

	Please let me know any ideas or comments the samba gurus have, as it will
b e greatly appreciated.


Thanks in advance


Patrick Harrold
Manager of Information Services
Nasco, Inc.
651.780.2000
FAX 651.638.1803
patrickh@nasco-inc.com

I have a problem with printing(2.0.3). I tried printing=sysv, and so on, but i
always get the following errors:
I can see the printers in the share browse list, but i just can not print.

I am using SCO openserver 5.

xiong

[1999/03/19 18:14:54, 3] param/loadparm.c:lp_load(2521)
  pm_process() returned Yes
[1999/03/19 18:14:54, 3] param/loadparm.c:lp_add_ipc(1495)
  adding IPC service
[1999/03/19 18:14:54, 7] param/loadparm.c:lp_servicenumber(2613)
  lp_servicenumber: couldn't find is1
[1999/03/19 18:14:54, 3] param/loadparm.c:lp_add_printer(1530)
  adding printer service is1

On 20 Mar 99, "Cityboy" <cityboy@itw.com> had questions about 
Greetings - Samba Help:  
> Sometimes linux appears in the network neighborhood and sometimes it does
> not.
> Info: Slackware 3.6 linux kernel 2.0.36
Most of my experience is with RedHat, but it should be applicable.
> ;   hosts allow = 192.168.1. 192.168.2. 127.
Uncomment this and put your IP address range in place of the first 
two (and make sure the loopback address in /etc/hosts is named 
"localhost").
> ;  guest account = pcguest
Browsing and printing require a valid guest account (eg, nobody, 
ftp, etc).
> ;  encrypt passwords = yes
Without this, current clients (NT4SP3, win98, win95 with updates) 
will require the EnablePlainTextPassword reg hack.
> ;   os level = 33
Crank this up to 65 if you want samba to be the master browser 
(hint: that's a good thing).
> ;   preferred master = yes
Uncomment this to give samba an edge in winning.
>    wins support = yes
Make sure the clients have WINS enabled, and the IP address points 
to the samba box.

Steve


*************************************************************
Steve Arnold                     http://www.rain.org/~sarnold

Linux:  It's not just for nerds anymore...

At 02:59 PM 3/22/1999 -0500, David Collier-Brown wrote:
>Could you send this to the mailing-list and/or the newsgroup?
>It's an interesting thing to have in the searchable discussions...
Original Problem: After a minimal setup of smb.conf, browsing worked fine
and files could be saved on the samba shares but when a file was retrieved,
some would retrieve OK, others would not. A great variety of error messages
were encountered. Several complained about wrong path names, and some
indicated that the network resource was no longer available. In several
cases win95 froze and required a re-boot. File retrieval was tried in a DOS
window, with explorer and by retrieving files into applications.

Test procedure (over a 2 month period)
1)Passed ALL tests in the troubleshooting guide included with the samba
distribution, in Blair's Samba reference, and in yet-to-be-published test
procedures.
2) Used tcpdump (smb version) to trace traffic. Copy sent to Samba team -
no abnormal behaviour identified. 
3) Since abnormal win95 client behaviour was suspected, compared versions
of the many variations of W95 (using listqfe and win95ver) to systems known
to work - all up to date. (My appologies to Steve Arnold, I lost the url
for these test files that you suggested)
4) Tried with 2 other clients (one on each of two subnets) one passed and
one failed.  (This really led me astray - I still do not know why one
passed! Perhaps not tested with enough different files?)
5) Since the client on the other subnet passed, I exchanged one nic for the
other in the samba host (same type of nic) with NO change in behaviour. The
clients continued to behave exactly in the same way as before the switch.
6) Tried ftp; ftp TO the samba server always worked. From the samba server,
ftp of small files worked OK but large files failed. (windows locked up in
almost all cases).  Ftp to/from other hosts worked fine.
7) Tried pings with larger (maximum) packet size - failed test (sporadic
timeouts/packet loss). Large packet pings to other hosts worked fine.
8) On large ftp transfers from the Samba host, tcpdump showed repetition of
many of the initial packets and then continuous repetition of the same
packet without response from the Win95 ftp client (usually frozen).

Solution: Concluded that the NIC was having trouble with transmitting
(formatting/buffering/other?) full packets, replaced it, and Samba works!
NIC may be less than 100% ne2000 compatible.

Post Mortem: Could have caught this sooner in steps 1 (with larger ping
packet sizes) and 2 (it showed the same behaviour as step 8 above).  Step 5
has me baffled but would not have helped even if the results had been the
same for both clients.  Perhaps I was too willing to blame Win95. However,
win95 should certainly be able to handle packet corruption more gracefully.  

Alex
Avantel Systems
Ottawa, Ontario, Canada

At school we have a Novell network and I would like to have samba so the 
students can create and share web pages. When I log in tto the Novell 
network I can't see the samba server. When I start windows I can cancel 
the Novell login then I get the windows login. Would that allow me to 
see the samba server?

Thanks,
Evan P.