HP3000-L Archives

October 1997, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Ken Vickers <[log in to unmask]>
Reply To:
Ken Vickers <[log in to unmask]>
Date:
Tue, 14 Oct 1997 10:32:36 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (81 lines)
Ted,

This looks like the experience we had getting Samba up.

NMBD running as the network browser was setting-up SMBD processes which
would not die and soaked-up so much CPU on our testbed 918LX that the
SHOWPROC on the console took ages to respond.

I dug through the 3000-L achives and borrowed some smd.conf entries, check
out INETDCNF, PROTOCOL, HOSTS, SERVICES, RESLVCNF etc., put in links for
all of those files which belong both in MPE and Posix.

Now when Windows95 PC's browse the network they can see this 918 but when
they try to connect up and the SMDB is launched the connection times out
and the SMBD closes down and the 918 carries on!!

I do not have an answer but I did a lot of tinkering with the configuration
and stopped this problem, but I still can not get Windows95 to connect up.

I believe that my problem relates to having a network connected to the
outside world through firewall and external DNS but no internal WINS or
DNS, so NT works but Windows95 does not.

The next time I have a day to spare I will try again to sort this out.

Ted Johnsonwrote:

>
>After being unable to earlier abort the JINETD job, we first tried doing
>a =LOGOFF keeping only the console connected.  When that didn't work we
>shutdown the network services and tried to shutdown the system with the
>=SHUTDOWN command.   The system hung for almost 15 minutes, so at that
>point we decided to do a <CNTL> B and reset the system.
>
>After the system came back up we started the network services and
>streamed the JINETD job.  At first users were able to connect using
>TELNET, but after 5-10 minutes they were locked out of their sessions
>and unable to reconnect.  We are also unable to abort the new JINETD
>job.  The only changes we have made in the past week was to load SAMBA
>on our system (without any success so far).  Our NS/VT users can connect
>without any problem as do our serial connections.
>
>Here is my SERVICES.NET.SYS file:
>
<snip>
.
.
<snip>
> Received call for: nmbp udp
> Received call for: nmbp udp
> Received call for: nmbp udp
> Received call for: telnet tcp
> Received call for: nmbp udp
> Received call for: nmbp udp
> Received call for: nmbp udp
> Received call for: nmbp udp
> Received call for: nmbp udp
> Received call for: nmbp udp
> Received call for: telnet tcp
> Received call for: nmbp udp
> Received call for: nmbp udp
> Received call for: nmbp udp
> Received call for: nmbp udp
> Received call for: nmbp udp
> Received call for: nmbp udp
> Received call for: nmbp udp
> Received call for: telnet tcp
> Received call for: nmbp udp
<snip>
_______________________________________________________
Ken Vickers
LINKWAY Development and Support
Computing Solutions Limited
10 St Andrews Road
Droitwich, Worcestershire
UNITED KINGDOM
TEL +44 (0) 1905 794400
FAX +44 (0) 1905 794464
mailto:[log in to unmask] or
mailto:[log in to unmask]

ATOM RSS1 RSS2