paulmew
asked on
Netware 3.12 / TCPIP
Hi guys, I'm trying to get TCP/IP running on my netware 3.12 server so I can get a web server up and running for an intranet. Unfortunately its causing some trouble. Clients get 'a network server could not be found' when running VLM.exe (or NETX). However, if I ping the server from the client or vice versa it pings ok. I've even tried turning off and on the client while it is being pinged by the server to ensure that the replied stop when the client is off... and they do. Any suggestions???.
Thanks to everyone in advance!!.
Thanks to everyone in advance!!.
ASKER
I'm using the latest TCPIP.NLM as posted at the netware web site, v4 I think, and how will moving to client32 sort the problem? (pardon my ignorance!).
Check your settings in the NET.CFG file.I'm assuming you're pinging in DOS and I also assume that you have 802.3 and II set up in there, otherwise you wouldn't be able to ping(?). In your NetWare settings, check the ARP settings. Is the server set to route the requests? That may be your answer. If the client can see the server, and the server can see the client, it comes down to what 3.12 is doing with the server requests.
I'm new to Netware, but I've had lots of hassle with TCP/IP. I've found that, with Unix, VAX and NT servers, I always needed to specify a default route (i.e. tell the server the IP address
of the local gateway/router. Even with my DHCP server, i had to put in parameters for a default route. That said, I don't think you could ping successfully unless this was done.
I used to use LSL, then the card driver, then the IPXODI driver, and then whatever driver you want (netx, VLM, etc). They have to be loaded or unloaded in this order, and when we were troubleshooting, we ran each driver separately, to check each one worked. You probably know all of this, but if not, check it out.
of the local gateway/router. Even with my DHCP server, i had to put in parameters for a default route. That said, I don't think you could ping successfully unless this was done.
I used to use LSL, then the card driver, then the IPXODI driver, and then whatever driver you want (netx, VLM, etc). They have to be loaded or unloaded in this order, and when we were troubleshooting, we ran each driver separately, to check each one worked. You probably know all of this, but if not, check it out.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
please grade my answer
Why don't you move to Client 32?