Jcranmer

Okay here goes. I have a remote site that has an OLD novell 3.1 box that we need to be able to access over the WAN.

I have been told by the person that takes care of this server that 3.1 can't do tcp/ip.

1) Can anyone who has actually used NW3.1 confirm this??
2) If it can't, can someone point me in the right direction for trying to figure a way to route IPX/SPX packets? To make matters even worse, this is NOT a direct connection between us and this remote site, we hop through at least one other location to get there, so there would be at a minimum of 4 cisco routers involved.

Currently the way we are getting to it, is that we have a machine running PCAnywhere on their network with the novel drives mapped. We can then use tcp/ip to get to the pcanywhere box to get the files we need. This works, but it's not an ideal solution.

Hopefully there are a few here that are old enough to remember the days of Novell 3.1

GilbertsGrape

yep they are correct, i once had a novel 3.11 server a while back no TCP/IP on that puppy. we used it along with our Win 2K servers, the way we used it was by installing IPS/SPX on the client machines and installing the client for novel networks then setting the server in the configeration of IPX / SPX and the netware client.

Anothe option i thought about is not sure if it will work or not but if you a have a Windows server you can install IPX /SPX on it and novel cleint and then just map the novel drives on the server and then share the maped drives from the windows server. can should probably be able to do this on that Workstation your sahring with PC anywhre instead of using PC anywhere just turn on the file and print shareing and shre the mapped drives. and if you cant see the workgroup that the client that is sahreing the maped drives on then just go to start > run> tehn type "\\shareing IP of server\" and then you should see all shared items on that PC. printers drives ect.

Joshua

Netware 3.11 does not support tcp/ip by default.

Download this nlm and install it to get tcp/ip support in netware 3.11.

Note the Netware 3.11 section under the Installation Section.


NOVELL TECHNICAL INFORMATION DOCUMENT

TITLE: Common TCPIP.NLM for NW 3.12 and 4.x
README FOR: TCPN03.EXE

NOVELL PRODUCTS and VERSIONS:
NetWare 3.12
LAN WorkGroup 4.2
NetWare FLeX/IP 1.2C
NetWare NFS 1.2C
NetWare NFS Gateway 1.2
TCP/IP 2.x
NetWare MultiProtocol Router 3.0
NetWare 4.02
NetWare 4.1
NetWare NFS Services - NetWare 4 Edition 2.1
LAN WorkGroup 5
NetWare IP-NW312
NetWare IP-NW410
NetWare MultiProtocol Router 3.1
NetWare WEB Server 2.5
ManageWise 2.0
ManageWise 2.1
NetWare 4.11
Web Server - Web 2.51
MPR IW 4.11
NetWare WEB Server 2.51
TCPIP IW 4.11
IntranetWare NFS 2.12
Novell Web Server 3.x

ABSTRACT:

This file contains a new TCPIP.NLM (v4.00) that runs on all LAN (3.12,4.x) and
WAN (MPR 3.x) platforms. Also included is a seperate stack for customers
running
in a Netware 3.11 environment for backward compatibility (doesn't include any
of
the new features).

(Obsoletes TCPN02.EXE)


-----------------------------------------------------------------
DISCLAIMER
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL
MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION. HOWEVER, THE
INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL
MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION.
-----------------------------------------------------------------


ISSUE:


New Features:

------------------



1. Common TCPIP for all netware platforms >= 3.12

2. path MTU support

3. Improved TCP interface for customers using TCPIP on 3.X

4. TraceRoute module for Netware Server (IPTRACE.NLM)

5. Enhanced TCPCON to flush routes in your routing table

6. IP Multicast support

7. New APIs support (Nagle, delayed ACK)

8. support for multihoming

9. support for fast path algorithm

10. support for automatic IP address assignment over PPP

11. ShortHold (from client to Server and also from Server to Client)

12. DNS aware PING.NLM

13. Support for all 1's in subnet mask



Problem Fixes:-

------------------



1. stack hangs when TCP connections in the syn-recieved state

2. problems with sends of reverse ARP queries over Frame Relay links

3. loss of static route information when WAN links go down

4. fixes TCP RESETs when large file transfer during NW -> AS400





Note 1: Customers running an OSPF ASBR on a server running this version of
TCPIP.NLM may encounter problems and should refrain from installing this patch
ie. continue to use the version of TCPIP that they were using before.




Self-Extracting File Name: tcpn03.exe

Files Included Size Date Time

..\
TCPN03.TXT (This file)
TCPN03.TXT 8028 7-29-97 6:18:02 pm
..\DISK1\
PINSTALL.HLP 5582 2-3-97 7:05:00 pm
PINSTALL.NLM 168811 2-25-97 9:32:02 pm
PSCRIPT.DAT 4379 6-5-97 12:45:28 am
README.TXT 1390 3-19-97 5:58:10 pm
..\DISK1\RINSTALL\
PINSTALL.IPS 340 3-19-97 6:05:02 pm
..\DISK1\TCPIP\
CSLIND.NLM 11763 2-20-97 11:35:28 pm
IPCONFIG.NLM 858 2-11-97 12:48:20 am
IPFLT.NLM 2012 2-28-97 11:12:42 pm
IPFLT30.NLM 21196 4-26-96 4:18:34 pm
IPFLT31.NLM 77280 2-28-97 8:41:30 pm
IPTRACE.NLM 10694 2-11-97 1:11:16 am
MPRDINST.NLM 4637 5-19-97 7:12:02 pm
PING.NLM 41462 2-11-97 1:12:40 am
TCPCONV.NLM 172954 2-11-97 12:55:30 am
TCPSTCNV.NLM 158548 2-11-97 12:58:30 am
TPING.NLM 4768 2-11-97 1:11:50 am
..\DISK1\TCPIP\NLS4\
IPTRACE.MSG 928 2-6-97 4:52:36 pm
PING.HLP 5148 11-22-95 9:55:50 pm
PING.MSG 1085 2-6-97 4:56:54 pm
TCPCONV.MSG 4550 2-6-97 12:45:12 am
TCPSTCNV.MSG 3150 2-6-97 12:48:12 am
TPING.MSG 662 2-6-97 4:53:08 pm
..\DISK1\UTILS\
CSLCNVRT.NLM 18508 2-5-97 5:15:16 pm
..\DISK1\UTILS\NLS4\
CSLCNVRT.MSG 726 2-5-97 5:15:10 pm
..\DISK2\
..\DISK2\SNMP\
SNMP.NLM 100093 2-18-97 5:48:32 pm
SNMPLOG.NLM 14114 2-6-97 9:47:52 pm
..\DISK2\SNMP\NLS4\
SNMP.MSG 4064 2-6-97 9:47:16 pm
SNMPLOG.MSG 615 2-6-97 9:47:52 pm
..\DISK2\TCPIP\
TCPCON.NLM 241610 2-28-97 8:55:30 pm
TCPIP.NLM 484494 2-28-97 7:21:44 pm
..\DISK2\TCPIP\NLS4\
TCPCON.HLP 100557 2-24-97 6:24:14 pm
TCPCON.MSG 29173 2-6-97 12:59:24 am
TCPIP.MSG 18224 2-6-97 10:07:02 pm
..\NW311\
311.TXT 1190 5-16-97 5:55:16 pm
AFTER311.NLM 11738 1-26-93 11:45:30 pm
BOOTPFWD.NLM 7991 9-13-95 8:26:20 pm
IPCONFIG.NLM 11766 9-13-95 8:14:00 pm
IPFLT.NLM 984 9-13-95 8:28:02 pm
NWSNUT.NLM 175546 10-17-94 9:14:20 pm
PING.NLM 41198 9-13-95 8:25:34 pm
SNMP.NLM 85974 9-14-95 9:33:46 pm
TCPCFG.NLM 184613 9-8-95 12:12:04 am
TCPCON.NLM 230611 9-13-95 8:24:02 pm
TCPIP.NLM 392545 9-13-95 8:11:52 pm
TPING.NLM 4771 9-13-95 8:24:40 pm
TUI.NLM 43415 11-22-94 7:18:56 am


Installation Instructions:

Installation instructions
=========================

A:- For Netware 3.11 Servers only!!!!

1. Make a backup copy of each NLM file specified in the NW311 directory.

2. Manually copy the NLM files from the NW311 directory to the SYS:\SYSTEM
directory.


B:- For all other platforms

1. To install from floppy, you will need two 1.44MB floppies.
1.1. COPY DISK1\*.* A: /S/E/V
1.2. LABEL AISK1
1.3. COPY DISK2\*.* A: /S/E/V
1.4. LABEL AISK2
1.5 Load install at server console and enter A:
for the installation path.

2. To install from local system volume:
For example:
2.1. Create a TEMP Directory (sys:temp) and put DISK1 and DISK2 there.
2.2. Load install at the server console and enter
SYS:\TEMP\DISK1 for the installation path.

This additional installation method only runs on 4.1x servers.
================================================
3. To install from a workstation to any 4.1x server
3.1 Create a TEMP on any drive (local or network) and put DISK1 and DISK2
there.
For example:
C:\TEMP\DISK1 or F:\TEMP\DISK1
\DISK2 \DISK2

3.2 If Rconsole and remote install are not already enabled, then enable
Rconosle and remote install on the remote server via INETCFG.NLM and
reinitialize system.

3.3 From your client, Rconsole to the remote server.
For example:
F:\public\Rconsole <target servername>
Provide ADMIN password and load INSTALL at the server console.

3.4 Make sure you Press <F4> instead of <F3> or <ENTER> when asked for
source path and then enter C:\TEMP\DISK1\RINSTALL or
F:\TEMP\DISK1\RINSTALL.



-----------------------------------------------------------------
Any trademarks referenced in this document are the property of their
respective owners. Consult your product manuals for complete trademark
information.
-----------------------------------------------------------------

__________________
The Apexer formerly known as SnotRocket.

"Like I ****ing said, "Ok, so I hear it may be a repost. Blah But I had never seen it, so..." **** you Canta." -Jenny 12/4/2003

Jcranmer

Thanks! I will give that a try. (crossing fingers this works, cause I don't want to go to Kansas to fix this thing if I break it!)

bbrian

I ran 3.12 and had TCP/IP loaded on it.. kinda buggy, but it works.

The problem with using IPX/SPX is each of the hops between you and the server need to support IPX/SPX too. If they already do, then most likely you wouldn't have any problems connecting already. If any of those hops is over the internet you can foget it unless you can get a VPN tunnel setup and route IPX/SPX though it.

Joshua

Did it work?