General discussion

Locked

NT SQL & Transaction on a Novell based W

By Gareth Eyers ·
We have a mixture of Novell 4.1 and 4.11 servers, all with the latest service packs.

Theses servers are spread out over several offices connected via WAN connections.

The clients use Client32 to connect to their local servers

The network protocols are IPX/SPX

We do NOT have TCP/IP and it is not an option at this time to install TCP

I need to connect a windows NT4 server running SQL7 and transaction server to this Novell environment.



From what I understand, the DCOM agent on the clients talks to the transaction server, this in turn talks to the SQL Database.



Is it possible for transaction server to run in an IPX environment and talk to the clients? I know that SQL can use IPX as well as named pipes



If so how do we go about configuring the NT server to accomplish this?



The solution needs to be server based, I am able, if I install the windows connection client and TCP, to run the database, but as all our clients are all over the USA it is not feasible to gain c

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

NT SQL & Transaction on a Novell based W

by Ron Navon In reply to NT SQL & Transaction on a ...

Dear Sir,

I am working so in WAN with NT include MS SQL 7, Sybase, Oracle, and Novell 4.11 in IPX/SPX that all of them is full integrated.

Please install the GSNW service on your NT server and you have pay attention in network ID when you configure the IPX/SPX protocol .

If you give the same Network ID you can not to connect from NT to Novell.

The Id Network number like " 100100011"

I hope it is help you.

Best Regards. Ron

Collapse -

NT SQL & Transaction on a Novell based W

by Gareth Eyers In reply to NT SQL & Transaction on a ...
Collapse -

NT SQL & Transaction on a Novell based W

by davide In reply to NT SQL & Transaction on a ...

The performance of the system MAY suffer a hit using only IPX vs IP depending on the client access libraries the app vendor included in their program. The main reason being that the client side DCOM is TCP/IP optimized with other protocols essentially crippled by getting thunked into 16 bit code. This performance hit may not be noticeable though on the remote segments coming into the SQL server over the LAN - but will definitely be noticeable on a local connection. Depending on your app vendor, they may even deny support to a MS SQL server app until you're running TCP/IP. Don't want to bum your day, but just another MS "you will be assimilated" problem.

Collapse -

NT SQL & Transaction on a Novell based W

by Gareth Eyers In reply to NT SQL & Transaction on a ...
Collapse -

NT SQL & Transaction on a Novell based W

by alsanchez In reply to NT SQL & Transaction on a ...

This might sound trivial but you have to add the clients to the NT domain. You must also add the SQL database to the ODBC. You may use either IPX or named pipes there are pros and cons to which ones you use and also configuration issues. Good Luck.

Collapse -

NT SQL & Transaction on a Novell based W

by Gareth Eyers In reply to NT SQL & Transaction on a ...

Related Discussions

Related Forums