2.2 Client / Gateway

[Dave Widdifield]

What registry entries are made on a 2.2 client running the gateway? Many
admins are reporting problems upgrading 2.2 clients to 3.3 without the
gateway. When running WINIPCFG to confirm the DHCP setup, we get the "Fatal
IP configuration" error. The clients have been uninstalled using the
appropriate UNC32, TCPIP has been removed and reinstalled, the old
WS2BAKUP.BAT file was run both from DOS and from within Windows 95. I am at
a loss as to where to look.

Dave

[Craig Johnson]

That is an issue of mixed Winsock file versions. Here's the basics,
you can figure out the specifics.

Win95 shipped with winsock1. BMgr 2.1 IP Gateway used winsock1 as
well.

Newer Client32 installations include updates to tcpip that upgrade you
to winsock2. However, if you have not installed the tcpip stack first,
or if you end up reinstalling something in Win95 that reinstalls the
tcpip stack, you end up with a mix of winsock1 and winsock2 related
files, and the classic symptom is the "Fatal IP configuration" error in
winipcfg.

If you run the ws2backup program (which is a Microsoft program, by the
way), it back-revs the files to winsock1, which seems like it gets you
working again. However, even if TCPIP is then functional, you still
are not at winsock2.

You do not have the same issue with Win98 because Win98 came with
winsock2 files.

If you delete and reinstall the TCPIP protocol, and then update to
winsock2, you should be OK. I believe the MSDUN13.EXE patch provided a
winsock2 update for Win95, though there may be a newer patch out now.

I suspect you can find some more details on this in the Client32
forums.

Craig Johnson
Novell Support Connection SysOp

See http://nscsysop.hypermart.net for a book on configuring
BorderManager packet filter exceptions, and some hints, tips and files
for BorderManager.