Win NT4.0 Server Win95 Clients (AREV Specific) [Revelation On-Line Wiki]

Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 19 MAY 1998 01:41:25PM Scott Musselman sirmuss@if.rmci.net wrote:

AREV Specific

Problem:

Windows 95 clients can slow down to take up to 5 or more minuets to reach the main menu in arev where in normally takes only a few seconds.  If  Arev is slow it is slow from boot up the speed doesn?t change after boot. It is either slow or fast.  All other network tasks run at normal speed regardless of arevs speed.  If the workstation booted with 802.2 as frame type then switching it to 802.3 will speed it back up.  If workstation started with 802.3 then switching it to 802.2 will speed it up.  The workstations may work correctly for days or experience the problem again at next boot up. DOS workstations set for 802.2 never experience this problem.

             Scott Musselman

Reply here or: sirmuss@if.rmci.net

Server:

dual pent 200, 256 meg ram

Windows NT 4.0 SP3

NT Service 1.5

IPX/SPX main protocol, Frame type Auto

TCP/IP (for hp jet direct hardware)

Netware gateway (for e-mail system on novell server for NT DOS clients)

Arev:

2.12

NPP 1.5

revparam set to force use of linear hash

Clients:

~50 mixed between the following

DOS clients running win NT client for DOS

Win 95 machines running Microsoft networking client using ipx/spx

At 19 MAY 1998 03:58PM Skip Hill wrote:

I have a similar problem; NT40, Windows 95, Arev 3.12, NT Service Pack and All Networks driver. The boot up sequence (AREV SYSPROG) takes 2-3 minutes. When I change to Non-Networking, its up in 3-7 seconds. Little other server activity, plenty of Ram and processor available. REVPARAM file ServerOnly=True verified to work.

I'll be interested in responses, having read through many of the other threads, I have not found the magic elixir yet…

At 19 MAY 1998 05:42PM John Duquette wrote:

Scott,

The NT Service uses Named Pipes to communicate between the workstation and server which requires TCP/IP/NetBeui instead of IPX. So, I would remove IPX from the workstations/server if possible.

If that is not an option, i.e. you have Novell servers, install the client32 on the win95 workstations, and stack the protocols on the server so TCP/IP is first. This will split the protocols on the workstations so they should only talk to the NT server over TCP/IP.

John Revelation

At 14 JUN 1998 09:14PM John Stephenson wrote:

We have the same problem. Win NT server, Win 95 clients and Arev goes VERY slow quite often.

Do you have any ideas ?

View this thread on the forum...