🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.os.netware.misc
Article #593

Re: New 4.1 Server - can not connect to it - help

#593
From: harte
Date: Mon, 28 Aug 1995 00:00
51 lines
3191 bytes
In article <41kpq9$10v8_001@phoenix.net>, <jheil@phoenix.phoenix.net> writes:
> Xref: news comp.os.netware.connectivity:4083 comp.os.netware.misc:9845
> Path: 
news!newshub.nosc.mil!dog.ee.lbl.gov!agate!spool.mu.edu!howland.reston.ans.net!
newsfeed.internetmci.com!news.sprintlink.net!gryphon.phoenix.net!phoenix
> From: jheil@phoenix.phoenix.net (Jim Heil)
> Newsgroups: 
bit.listserv.novell,comp.os.netware.connectivity,comp.os.netware.misc
> Subject: New 4.1 Server - can not connect to it - help
> Date: Fri, 25 Aug 95 15:21:45 GMT
> Organization: KB5AWM
> Lines: 12
> Message-ID: <41kpq9$10v8_001@phoenix.net>
> NNTP-Posting-Host: dial56.phoenix.net
> X-Newsreader: News Xpress Version 1.0 Beta #3
> 
> We have an HP NetServer LC EISA 486/66 machine that has been set up as a 4.1 
> server.  We are having several problems with it. First, the server abends 
with 
> processor exception errors. It seems it has problems writing to the 
volume/fat 
> of a particular drive.  We changed drives and it seems to work okay.
> 
> Now we have a problem with the NIC. We had a RACAL EISA card in it but we 
> could not connect to it. So we put in a 3C509 card using the EISA  setup 
> instructions. The server can be seen from another server (display servers) 
and 
> the HP server can also be seen from a workstation. However, when we try to 
> cocnnect to the HP server the error "server not available" is given and the 
> drive is no longer valid (F:).  Weird.  Any clues out there?  This is 
> something I have not come across yet....until now :-) -- Jim

Make sure your workstations and 4.1 server frame types match.  

Also, try using TRACK ON on the server.  When you try to connect from a 
workstations, you should "Get nearest server" from the WS (IN), then "Give 
nearest server" from the server (OUT).  If you see this more than once, then 
the problem may be the NIC on the WS.  If you don't see this at all, focus the 
server.

Hope it helps,
Becki

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Becki Harte                 + "Any sufficiently advanced      +
+ CIO BRTRC                   + technology is indistinguishable +
+ 703.704.1486                + from magic."                    +
+ harte@nemo.nosc.mil         +                                 +
+ bharte@brtrc.com            +       -- Arthur C. Clarke       +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Technical Details
Message-ID: <1995Aug28.144559.25840@nosc.mil>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail
References: <41kpq9$10v8_001@phoenix.net>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fe659,b79d236e5274e46e
X-Google-Attributes: gidfe659,public
X-Google-Thread: f8bf7,b79d236e5274e46e
X-Google-Attributes: gidf8bf7,public
X-Google-Thread: fa939,b79d236e5274e46e
X-Google-Attributes: gidfa939,public
From: harte@nemo.nosc.mil
Subject: Re: New 4.1 Server - can not connect to it - help 
Date: 1995/08/28
Message-ID: <1995Aug28.144559.25840@nosc.mil>
X-Deja-AN: 109008959
sender: news@nosc.mil
references: <41kpq9$10v8_001@phoenix.net>
content-type: TEXT/PLAIN; charset=US-ASCII
organization: NCCOSC RDT&E Division, San Diego, CA
mime-version: 1.0
newsgroups: comp.os.netware.misc,comp.os.netware.connectivity,bit.listserv.novell