Networks

Even though when you upgraded your servers and IP was installed, did you configure the IP? You can use nwconfig to check the network protocols and their status. Is one of your servers configured as a DHCP server? You only need to do this if you're not using Static IP addressing. When setting up the IP networking it's helpful to know how many clients are involve the subnet 255.255.255.0 allows for up to 253 nodes. Typically I reserve the first 20 addresses for servers and reserve the upper 30-40 address for printers, routers and other network devices. Once you have configured the IP on the servers take one client and configure it only for IP and try to connect. If all goes well you can use nwconfig to unbind the IPX protocol from the server's NIC(s).

Hi Chris,
They can talk both, and they choose whatever protocol is available. It's easy to check if your workstations talk IP to your server, but you cannot really check what they use to check NDS talk among each other.

There are a few things you can do. First, check timesync: if you use IP, you need to use configured sources. Put an IP address in there, and type "set timesync debug=7" on the console. This will bring up an extra scren, and there it will show if the server sycnhronized (or not) with the server's IP address you wrote.

Second, a quick and easy check is to disable IPX one evening, just for a few minutes, via INETCFG.NLM (in the Protocols menu, don't forget to "reinitialize system). Then, type the following:
set ttf=on (enables trace to file)
set dstrace=*r (clears that file)
set dstrace=on
set dstrace=+s (this shows NDS sync messages)
set dstrace=*h (this forces a sync now)
(go to the Directory Services screen, and wait for the "All Processed=Yes" (or no) message)
set dstrace=nodebug
set dstrace=off
set ttf=off
Then you can enable IPX again via Inetcfg, and check sys:\system\dstrace.dbg. Most likely the server did do a sync, and if not, you'll see in there with which server(s) it had a problem.

A less obvious way is to check the server-to-server links in the Connections menu in Monitor.nlm. For each connection you should see either an IPX or an IP address. But there it is not clear which connection is used for what exactly.

By the way, before IPX is filtered, check if broadcasts will be filtered too. If so, look into the usage of SLP.

Jim

I need to know one thing about your wan. How are you routing the IPX packets through the router onto the WAN?

At the server console type "load ping <IP Address>" this will ping whatever IP address you put in. If you get no reply then they will not talk IP. If you do "config" at the console prompt you will see under LAN Protocol for IP your IP address and mask, howver you will not see your gateway. If you have transfered you config using "inetcfg" then the gateway will not pass over. You need to unbind IP and bind it again at the prompt and make sure the gateway is in.

This question was auto closed due to inactivity