From: jra@law7.DaytonOH.NCR.COM (John Ackermann x 2966)
Subject: Windows for Workgroups and TCP/IP -- problems
Reply-To: jra@law7.DaytonOH.NCR.COM (John Ackermann x 2966)
Organization: NCR Corporation -- Law Department
Date: Mon, 14 Dec 1992 14:13:29 GMT


We have several copies of Windows for Workgroups running with the MS
LanMan tcp/ip stack and a Unix server running MSNET1.0 over tcp/ip.  I
wonder if anyone else is having the same experiences we are:

1.  About 2/3 of the time Windows stalls during its attempt to access
the network.  The initial windows logo goes away, the wallpaper comes
up, the hourglass appears, but instead of getting the login window, the
system just hangs forever.

    You can then reboot the machine and try again, and it may well work.
This intermittent operation doesn't seem to depend on other network
activity (there is none).

    If the login prompt actually does appear, the system works fine and
talks to the MSNET server (but note below).

    Logging in under DOS works reliably and never hangs up.

    Is anyone else seeing this sort of problem?

2.  I seem to have problems copying files larger than about 50k across
the network to the server.  This again is intermittent, but I think is
probably related to the server being not too fast (about 50k per second
transfer rate with the MSNET software).  Sometimes large files will do
fine, other times the system will just hang up (requiring a reboot) and
an inspection of the server disk shows that only about 50k of the file
actually transferred.

    If this is a timeout problem, is there any parameter fiddling I can
do on the WfWG clients to improve the situation?  Any other ideas?
    

3.  Finally, I'd been using QEMM v6.00 with stealth and Windows 3.1 with
no problems at all.  But using the stealth option with WfWG causes all
sorts of nasty hangups during initialization.  Does anyone know if this
is cured with a later version of QEMM?

Thanks...

Newsgroups: comp.protocols.tcpip.ibmpc,comp.dcom.lans
Subject: WfWG and TCP/IP -- experiences to date
Expires: 
Reply-To: jra@law7.DaytonOH.NCR.COM (John Ackermann x 2966)
Followup-To: 
Distribution: world
Organization: NCR Corporation -- Law Department
Keywords: 

We have several copies of Windows for Workgroups running with the MS
LanMan tcp/ip stack and a Unix server running MSNET1.0 over tcp/ip.  I
wonder if anyone else is having the same experiences we are:

1.  About 2/3 of the time Windows stalls during its attempt to access
the network.  The initial windows logo goes away, the wallpaper comes
up, the hourglass appears, but instead of getting the login window, the
system just hangs forever.

    You can then reboot the machine and try again, and it may well work.
This intermittent operation doesn't seem to depend on other network
activity (there is none).

    If the login prompt actually does appear, the system works fine and
talks to the MSNET server (but note below).

    Logging in under DOS works reliably and never hangs up.

    Is anyone else seeing this sort of problem?

2.  I seem to have problems copying files larger than about 50k across
the network to the server.  This again is intermittent, but I think is
probably related to the server being not too fast (about 50k per second
transfer rate with the MSNET software).  Sometimes large files will do
fine, other times the system will just hang up (requiring a reboot) and
an inspection of the server disk shows that only about 50k of the file
actually transferred.

    If this is a timeout problem, is there any parameter fiddling I can
do on the WfWG clients to improve the situation?  Any other ideas?
    

3.  Finally, I'd been using QEMM v6.00 with stealth and Windows 3.1 with
no problems at all.  But using the stealth option with WfWG causes all
sorts of nasty hangups during initialization.  Does anyone know if this
is cured with a later version of QEMM?

Thanks...

-- 
John R. Ackermann, Jr.        Law Department, NCR Corporation, Dayton, Ohio
(513) 445-2966		      John.Ackermann@daytonoh.ncr.com
Packet Radio: ag9v@n8acv      tcp/ip: ag9v@ag9v.ampr [44.70.12.34]
Xref: sparky comp.protocols.tcp-ip.ibmpc:6901 comp.dcom.lans.ethernet:2782