>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:
Which version of TCP/IP do you have? Is it from LAN Manager 2.1a (or 2.2)?
If not, then you definitely need to get the latest version of DOS TCP from us.
Also, is there any way that you can upgrade your Unix server to LM/Unix 2.1?
>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.
How did you install MS TCP/IP? Did you use the instructions from the WFW
Resource Kit? Did you make sure to include the V86ModeLanas=<TCP LANA #>
in System.ini (under [386Enh])? You also need to add TimerCriticalSection=5000,UniqueDosPSP=TRUE, and PSPIncrement=2 under the same heading in System.ini.
> 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?
Let me know if you've done the above, and are still having problems. If
so, send me some mail with your phone number, and I'll give you a call.
>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?
This may be a result of needing to tune the above parameters, etc. TCP
should handle a slow server and/or slow links.
>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?
Unfortunately, QEMM in Stealth mode is not supported with WFW. I don't know
if a later version will help or not.
Alan Back
Microsoft Corporate Systems
>Thanks...
>
>--
>John R. Ackermann, Jr. Law Department, NCR Corporation, Dayton, Ohio
