• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 902
  • Last Modified:

Netware 5.1 and Dos tcpip client connectivity

We are trying to connect a DOS client with Netware 5.1 server through tcpip protocol.

We have created the required dos client by running the client creation tool in the netware client cd.

What configuration changes has to be made in the server to support tcpip based dos client.

  • 11
  • 9
  • 6
2 Solutions
[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

As long as ip is loaded on the server,you shouldn't have to make any changes at all.
http://www.novell.com/coolsolutions/tools/13555.html gives you a few options, including the also-no-longer-supported Client32 for DOS/Windows, which works with vanilla DOS as well as DOS/WIN3.11, VLMs, NETX, links to Veder's site, etc.
das711Author Commented:
I have tried the above links. When tcpip.nlm get loaded i am able to ping my netware 5.1 server.On loading client32.nlm it reports that it culdnt find/attach to any server.How to troubleshoot further?
The dos/win client32 is really an IPX application, so it requires you to have  IPX compatibility-mode (scmd.nlm) running on the server(s), and the migration agent running on a server in the network.  You also need SLP running (SLP.NLM) and it wouldn't hurt to have a DA set up. If you're running pretty-much pure IP already, you probably already have SLP all set up, but may not have the SCMD.NLM running on the server(s), and a migration agent (scmd.nlm /ma)

The documentation for the dos/win Client32 is at http://www.novell.com/documentation/client/c32dwenu/data/a7ppqip.html

For more information on 5.1 compatibility-mode and MA configuration, see:

das711Author Commented:
Let me make myself clear of what i am trying to do.

We have a netware 5.1 server with ipx only support and 20 diskless dos vlm clients.

We have a new branch connected via routers. As our routers doenst support ipx routing we are planning to have dos tcpip clients at our new branch.

Using inetcfg we have added the ip address to the server

Server is running with service pack 4 which comes along with the netware installation cd

dos tcpip client use the following files
rtssrv.lan frame=ethernet_ii

Contents of the net.cfg are
NetWare DOS Requester
Protocol TCPIP
      PATH TCP_CFG c:\

Link Driver rtssrv
      FRAME Ethernet_II

               Static Directory Agents = TRUE
               Active Discovery = FALSE
               DHCP = FALSE
               TIME-6-QUIT-DA-WAIT = 3
               TIME-10-WAIT-REG-DA-PASSIVE = 3
               Directory Agent =

We have loaded SLPDA with default options

SLPINO says DA is up

pinging the server was successful

load client32.nlm reports a file server cannot be found

how to proceed further.
das711Author Commented:
do we need to install DNS server?
No,I think you are missing a preferred server or tree statement in the DOS requestor of the net.cfg.

Look at this:

Do you have SCMD.NLM running, with the /MA option?  I'm kinda thinking that using IP with VLMs is like using IP with the DOS/Win Client32 - it's really an IPX program, so it needs some assist on the server side, perhaps.  'Specially since the VLM client predates the DOS/Win Client32...

Side note: Support Pack 4 (not Service Pack - that's a Microsoft thing) is very old.  NW5.1 is at SP8 now, which is over a year old already.  It's not unreasonable to think that perhaps there's something there...

You don't need the SCMD to be loaded.

I have used client32 in pure DOS/IP form on 5.1 network and it did work.
It's been about 3 years,but I did have it working at a customers site.

As fot the SCMD thing,you could just have an IPX only client and it would work too.

It might be easier, in that Novell says you shouldn't use the DOS IP client for production,but there are folks who are using an IP DOS client only and it works  just fine.
Can't just have IPX only client - they've got IP-only routers...

This TID explains why TCP/IP-only NCP connectivity isn't a supported use of the DOS/WIN client: http://support.novell.com/cgi-bin/search/searchtid.cgi?10061307.htm

To connect using VLMs, you do need to use both the preferred tree and the preferred server DOS requester options, because the VLM client is a little weak on finding things, but I remain a bit unconvinced on the idea of using the VLM client in pure-IP mode, since it was made before the introduction of pure-IP (NCP over IP) and isn't too likely to handle NCP requests over IP, which is kinda necessary for it to have any use as a NetWare client.

Even Veder doesn't use VLMs to connect via IP with his super-dos-boot-disk thing - he uses the NLMs (client32).  He even references the TID I posted above, along with http://support.novell.com/cgi-bin/search/searchtid.cgi?/10071852.htm 

Perhaps by using SCMD you can work around some of the "pure-IP" issues with the DOS client mentioned in those TIDs and referenced by Veder.  Could be why it's mentioned in the DOS/WIN client32 documentation, perhaps?

I don't remember if there's a compatibility-mode setting in the DOS/Win Client32, but if so, I'd recommend using it, along with SCMD on the server.

The only alternative, and I really hate to suggest it, would be NWIP.

>Can't just have IPX only client - they've got IP-only routers...

Yes,you can.

Compatibilty mode encpsulates IPX packets in in IP packets.(not unlike NWIP)
So if he were to use SCMD, the server that is running SCMD will pass IP encapsulated IPX packets over the router(not IPX).
I have done this when I migrated a 4.11 NWIP to 5.1 pure IP.

My first  5.1 server was running SCMD as a migration agent.
My branch servers were running SCMD and pointing to the main branch server.
My clients ran IPX only at the branch offices and were able to talk to the main server.
But then again ,my branch servers were 4.11.
The asker still can't have IPX-only clients even with compatibility-mode, unless they put up a migration-agent and have a  server at *both* sites.

They just want client connectivity across the WAN, the way I read it, which means they'd have to use IP from the client to the server, so if there's a compatibility-mode feature of the DOS/Win Client32, then that's the way to go.  It almost sounds like it's built-in, from the way the Novell documentation reads.  For the sake of expedience, I will bend the rules a tad and cut'n'paste from a copyrighted work, so all can see what I'm talking about.

NOTICE: The following is an excerpt from the Novell documentation for the DOS/Win client32, copyright Novell, Inc.  Since it's a text reinterpretation of the document, where the trademark symbol (tm) would normally be in a smaller font and superscripted, it's in the same font and pitch, so where you see ClientTM and IPXTM and 5TM, imagine the "TM" being little letters vertically top-justified... ;)

<start excerpt>
Novell Client for DOS and Windows 3.1x is an IPX Application

The Novell® ClientTM for DOS and Windows* 3.1x is an IPXTM application. It can connect to IPX-only, IP-only, or mixed networks. NetWare® 5TM IP-only servers must be running Compatibility Mode (scmd.nlm) and the network must have a Migration Agent on a NetWare 5 server.

Compatibility Mode allows IPX applications to function in IP-only networks. Compatibility Mode also allows workstations to communicate with services in IP-only networks if the Migration Agent is installed on any NetWare 5 servers. Compatibility Mode is dependent on the Service Location Protocol (SLP) for its operation.
<end excerpt>
I thought he added a server at the branch office too.

But still it can be done with an IP only boot disk and not using compatibilty mode drivers.
As I said before ,I have done it and it works because we needed a boot floppy to bring down Ghost images to the users desktops and I created one.

And the folks at Cool Solutions have done it too.

das711Author Commented:
Thank u all for posting ur valuable comments n suggestions.

First i am trying to connect a pure dos ip client to the server within the network and then try it from my new branch.

While trying client32.nlm says "A file server cannot be found"

If i use ipx instead of srvloc.nlm in the client i am able to connect which indicates my server is working for ipx.

pgm554: Using a DOS boot floppy to bring down a Ghost image is WAY different than using it as a DOS client.

das711: have you loaded SCMD.NLM, as the documentation I linked to recommends?  Are you populating the PREFERRED TREE setting?  If you are using th tree name in the PREFERRED TREE setting, do you have the tree name being resolved in your HOSTS file?  

Since you don't have DNS, you should have a local HOSTS file with the names/addresses of your servers on the PCs.  Included in the HOSTS file entry for the server IP address, you should have both the server name and the tree name, ex:         myserver     mytree
Maybe,but the entry would be under resolve.cfg

>pgm554: Using a DOS boot floppy to bring down a Ghost image is WAY different than using it as a DOS client

Right now he just can't connect using IP.
And as I mentioned before ,Novell does not recomend using a DOS only client.
But if he wants to try it,remember that caveat.

Hmmmmm....What's up with Novell's site?
Still down?
Dunno.  Some pages work, some don't, like the documentation pages... grrr.

Re: hosts file/resolve.cfg - I couldn't remember *what* it was called with the dos/win client32 IP stack, but generically speaking it's a "hosts" file.

Funny thing is, Novell uses "resolv.cfg" on NetWare for the DNS resolver list.

Re: connecting - he can ping, so he should be able to connect.  Probably some minor tweaking of the NET.CFG file.  Like I mentioned, the VLM client needs to have both preferred tree and preferred server specified, and if there's no DNS and no functional SLP, there won't be anything to resolve the tree name or server name...
Also, like I said, the VLM client won't give him a pure-IP (NCP-over-IP) connection, so even if he could log in pure-ip, it would be otherwise useless, hence the need to use the 32-bit client (the NLM not the VLM).

The alternative, although it may be obsolete and a bit messy, would be to set up NWIP.  That would tunnel IPX in IP for him, so the IP-only router should work OK...
das711Author Commented:
Once again my heart felt thanks for all.

My connectivity problem has been solved.

I erased all my dos 32 bit client files.Extracted a fresh copy of files from srvinst2.exe .

The problem is caused by the version of trannta.nlm file. one is of the year 1998 and other of 1999.first is of 21kb n other is 38kb.

21kb size trannta.nlm worked for me.

Even without preffered tree n server option,DNS its working.

Pgm554 link explains this. this dos 32bit ip based client works like a full fledged novell client.

NWIP is only applicable for netware 4.11 and not for 5.1

I am planning to have a replication server image at remote end so user can have faster access at the same time replication will take place at the backgnd using the total band width

ur recomendations and suggestion needed.
New NetWare has "branch office" which is essentially a replicated server, backed up at the main site.

For 5.1 you'd probably have to use a 3rd party program, off the top of my head...
>NWIP is only applicable for netware 4.11 and not for 5.1
There is an NWIP release for 5.1 and it does work,but is not officially supported by Novell.

How many users on your system?
You can buy a server license for 5.1,but if you have less than a 100 users ,you might want to look at Novell SBS 6.6.
5 server licenses (including Branch Office appliances).
Novell did not start the unlimited server tree thing untill 6.0,so you have a few tough decisions
das711Author Commented:
I would like to share the points eually and award it  for both shineon & pgm554

Featured Post

Prep for the ITIL® Foundation Certification Exam

December’s Course of the Month is now available! Enroll to learn ITIL® Foundation best practices for delivering IT services effectively and efficiently.

  • 11
  • 9
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now