[Webinar] Streamline your web hosting managementRegister Today

x
?
Solved

DOS IPX Header different than NLM IPX

Posted on 1997-09-03
5
Medium Priority
?
377 Views
Last Modified: 2012-06-21
I am trying to write a program with a DOS client and a Netware server NLM. The problem is that the DOS IPX and ECB headers are totally different than that of the Netware NLM IPX and ECB headers. Should I use the DOS headers with the NLM? Will this crash the server or will the Netware automatically add the rest of the DOS packet to form a Netware packet?
0
Comment
Question by:Claude050897
  • 3
  • 2
5 Comments
 

Accepted Solution

by:
bkc earned 100 total points
ID: 1590588
The IPX packet format is the same across all platforms. The ECB structure is platform dependant.

You can not use the DOS ECB header in an NLM because pointer formats are different and the completion routine types are different.

I suggest you examine using TLI on the NLM side. We have implemented several SPX/IPX based DOS TSR's that communicate with
NLMs based on TLI for IPX and SPX.

Although I dislike TLI for TCP apps, for IPX and SPX its a better way to go as it allows you to treat IPX and SPX connections as
data streams.

Also, you must use TLI to take advantage of SPX II in an NLM.

Check out the developer NLM examples for server-side TLI IPX and
SPX programs.

0
 

Author Comment

by:Claude050897
ID: 1590589
Thanks, this will help very much. I have compiled and tested the SDK example for tli /dev/nspx but I get connection failed each time. Do you perhaps know how RSPX work with RConsole and if there is a SDK available for RSPX?
0
 

Expert Comment

by:bkc
ID: 1590590
Are you trying to write on own rconsole?

The tli /dev/nspx examples require that you have spxs.nlm loaded
(and tli.nlm, streams.nlm), do you have these loaded?

If you have Netware 3.12 without patches, look for strtli4.exe patch (or a later one) that updates streams, spxs and tli.

Also, you can't run the client-side tli example without also having the server-side example running, otherwise there isn't an
spx socket listening for a connection.


0
 

Author Comment

by:Claude050897
ID: 1590591
I actually just got it going. The problem was that the address required to connect should be the INTERNAL node and network address of the server and not that of the actual network adpater which can be found with the CONFIG command. And no, I'm not trying to write my own rconsole, but just thought that RSPX might work the same as SPXS and IPXS. So all of this means that I now have to have a DOS client also working with TLI and that has to know the internal node and network address of the server it want to communicate with...
0
 

Expert Comment

by:bkc
ID: 1590592
Your DOS client can use standard old IPX and ECB stuff, that's what we use. TLI is too big on DOS, in my opinion.

Its true that the server-side endpoint address will be based on the internal network number of your server.

If you use AdvertiseService() in your NLM, your DOS program can use SAP services to obtain the correct IPX address, you don't have to hard code it.

You can obtain a block of SAP codes and known sockets from Novell for use by your application. just request this through devsup. This way you can be assured you won't be colliding with any other
application. Using a fixed SAP type, and optionally a fixed SPX/IPX socket number makes it much easier for your DOS program
to locate the IPX address of the server via the Sap functions.

We use QueryServices on the DOS side to locate the NLM's IPX
address and socket number based on a pre-determined SAP type.

0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The following article sheds light on easy-to-use steps to recover non-responding hard drives without data loss. Count on these approaches to fix undetectable, not responding, or non-working hard drives.
There’s hardly a doubt that Business Communication is indispensable for both enterprises and small businesses, and if there is an email system outage owing to Exchange server failure, it definitely results in loss of productivity.
Is your OST file inaccessible, Need to transfer OST file from one computer to another? Want to convert OST file to PST? If the answer to any of the above question is yes, then look no further. With the help of Stellar OST to PST Converter, you can e…
Get the source code for a fully functional Access application shell with several popular security features that Access VBA application developers desire, but find difficult or impossible to figure out how to code. You get the source code for managi…
Suggested Courses

591 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question