Networks

Ask something
Discussion Locked

4.11 TCPIP problems

0 helpful
6 replies

by q2ggirl

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I configured TCPIP on a NetWare 4.11 server yesterday. I enabled the TCP/IP protocol and bound TCP/IP to the card. I reboot the server and was able to ping it. Today I am not able to ping it. What could have happened and what do I need to check?

Under Protocols:
Enabled TCP/IP status, IP Packet Forwarding enabled Router, RIP enabled, everything else is disabled.

Under Bindings:
the IP address listed
subnetwork mask of connected network: FF.FF.FF.0

RIP Bind options:
shows NIC card
status enabled, RIP mode RIPI

Expert TCP/IP Bind options:
Use of ARP enabled
Force proxy ARP diabled

6 replies

by jimbb

You don't say anything about a gateway, is the server on the same LAN segment as your PC? If not, you may need to add a gateway: Load inetcfg/Protocols/TCPIP/LAN Static routing (enabled), and in LAN Static Routing Table, the "default route" should be the address of your router. If there is one of course.

Try "Load ping" from the server, and see if you can ping loopback (127.0.0.1), the server's address, and from there step by step boxes "further away" from the server. Do the same on your workstation. This is the simplest method to figure out where the connectivity "ends". The reasons for that limit can be a lot:
-none or incorrect default gateway (on server and/or ws, or even some box in between)
-difference in subnetmask (ff.ff.ff.0 on srv=255.255.255.0 on ws)
-an internet connection may be used by either ws or srv to look for a route that of course isn't there.

If you want to check via which route your ws attempts to reach the server, type "tracert xx.xx.xx.xx" in a command prompt (xx.xx... is the IP of your srv.) on your ws. On the server "load tcpcon" can show you where the srv thinks that other devices are. Maybe it has discovered a router that is no longer there or no longer reachable?)

Yeah, IP problems can mean a load of fun before you find them...

Jim

by q2ggirl

Thank you for your comments. I'm having IPX/SPX problems that started the next day I'm hoping as a coincedence with me having added IP to the 4.11 server.

The bad thing is, the sever connects directly to the switch that diretly feeds into the router, so there is no moving further away process.

Would Cicso router changes have messed up the routing table enough to where SPX can't route to a remote location on our network? I went to a remote location from our main site that is about physically 5 minutes away. I can see the server in Network Neighborhood, but cannot log into it or authenticate to it. However, I am able to ping it. Also, it's listed in RCONSOLE, but it gives an error message that states that SPX is not communicating so I am not able to RCONSOLE into it either.

Any more suggestions?

This discussion is closed to new replies.