Client's Protocol Changes

[SuperDaveDCF]

I've got a new 5.1 sp3, ZEN 3.2 server in another city that I am about to migrate users to. I've created an ACU to install Client 3.32. I've set it to install IP and IPX but to use IP as the preferred protocol. There are some other settings for forced logins, file caching, remote management, etc.

When I login to that server from my building the ACU installs the new client as it should. The settings look good as well. The one glitch is that after the reboot and subsequent login, I get an IPX connection to that server.
If I use the same workstation to login to the server in my building I get an IP connection. Subsequent logins to the new server or other servers outside my building also give me IPX connections.

Any ideas?

 

[TheLad]

You need to ensure that your routers are routing IP, failing that I would try enabling IP routing on your server. -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[SuperDaveDCF]

I'm assuming that the routers are routing IP as no one has complained about Internet or mainframe access issues.

How do you enable routing on the server?

 

[salserocito]

If you are running INETCFG, go there and select Protocols/TCPIP/IP Packet Forwarding and make sure that you have it set for ENABLED "ROUTER", not DISABLED "END NODE".

Good Luck!

 

[TheLad]

Be advised that the network should route IP for you, not the servers. We have found increased traffic on the LAN/WAN when IP routing is switched on from the servers.

All of the servers at my current contract have IP Routing switched off, however at a previous contract they had to have it switched on due to the network being pants and not routing IP properly. -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[SuperDaveDCF]

Thanks for the replies guys! A little more research found something very interesting with this TID:

http://support.novell.com/cgi-bin/search/searchtid.cgi?/10057730.htm

The default W95/98 client install sets the Name Cache Level to 1 which apparently means that the server's IP/IPX address is held in memory on the workstation. Setting this to 2 is called "persistent". The addresses are stored in a file called C32NMCAC.CAC in the c:\novell\client32 directory. This file is read into cache during a reboot.

Also, the default name resolution service for the IP protocol is NWHOST. This is a text file also located in the c:\novell\client32 directory. Simply editing this file with the server name and IP address forced my test workstations to connect IP to the servers outside my building. This file is included in the unzipped client files. I plan to edit this to include all of our servers and then I hope it will overwrite the current file when we do our ACU next week.