Connecting to WinNT4 & Novell 4.1 at the same time...

[GEllington]

I have two separate networks in my business. One is running Novell 4.11 & the other Windows NT4.

For security reasons, I am absolutely NOT going to link the networks/servers themselves. But I want to be able to access either or both of them from my personal workstation.

I thought it would be as simple as installing a second NIC, and binding the TCP & IPX protocols to the proper clients, but this doesn't seem to work.

I can use either NIC to connect to either network (by moving the cables around), but cannot find any way to make my workstation (Win98SE) connect to BOTH networks at the same time.

Any suggestions?

 

[dpellegrini]

You should be able to connect to both networks from one nic with out having NT and Novell integrated at the server level. MS will use MS-TCP/IP which won't communicate with novell, and Novell will use IPX through client 32 access. Bind TCP/IP to your nic, but only have it bound to Client for microsoft networks. IPX can be bound to only Novell's client 32. This should work just fine. If you are using Novell's IPX/IP gateway, there are other considerations. Hope this helps.
Domenick

 

[unit512]

I agree with the above. That is what we do here..except we have IP on Novell and NT.
We make sure the names and passwords in NT match those in Novell.
The system will then log in to both servers with one password.

 

[GEllington]

YES!

Believe it or not, I have been trying (off an on) to get this to work for over two years.

Your assistance is GREATLY, SUPER, SUPREMELY appreciated!!!

But, ummm... You said I could do this with just ONE nic?

Right now I have the protocols & clients bound to the appropriate card, with a Cat5 cable going to each network hub. How could I do this with just one NIC?

 

[unit512]

We put some smoke and mirrors into the pci slot

Seriously...

In Network Properties

You want Clients:
Client for Microsoft Networks (NOT Windows Logon)
Client32 for Novell

Adapter:
Nic Card
Anything else you want

Protocols:
Novell IPX/SPX
Microsoft TCP/IP
Bind both protocols to a single NIC

Set up the IP with an addresses if you are not using DHCP

Highlight Client for Microsoft Networks
Under properties make sure Log on to Domain is filled in properly

At that point we set Client32 as the primary log in
(though it does work the other way) and everything
just flows.

Also are you using NT login scripts? If so, they should run
after the Novell login script.

Keep me posted.


We login via Client 32.

 

[GEllington]

I know I am being really stoopid here, but how am I going to connect to both networks if I have no PHYSICAL connection (currently via the second NIC)?

 

[unit512]

I am assuming...

1 Novell Server - 1 nic
1 NT Server - 1 nic
## Work Stations 1 nic in each
1 Hub or Switch

Plug everything into the (same) Hub

Dump that damn second NIC

 

[GEllington]

"ahhhh, I see, sez the blind man"

Thanks, I understand now... unfortunately the physical layout of the servers and hubs (three hubs total) will make that impossible for now. Next time I wiggle some upgrade money out of the VP, I'll use some of it for a good switch to replace all three hubs.

Thanks again for the help.

 

[unit512]

If you can daisy chain or cascade the hubs
that will work too

 

[dpellegrini]

Yeah, or if it truely is 2 separate networks (separate hubs, etc.) not connected, then the 2 nics will work as well.

 

[DrGreen26]

OK OK OK...here is something you need to consider If you are accessing the NT server and the NT server is on the other side of the Router Boundary (since you have 2 networks) you need to implement an LMHOST File. Without it, you would need a WINS server <--- Not advised to do this, but here is an example of what we needed to use to access 2 NT servers on a DOMAIN

10.10.7.129 TEXTCOMPDEV #DOM:TEXTCOMP #PRE
10.10.7.128 TEXTCOMPPROD #DOM:TEXTCOMP #PRE

Do not change the extension of the LMHOST file, if you do, NT/98 will not read it properly. Also, if you are accessing the NT server with a win98 Machine, you must install the MS Client in addition to the Novell client. If you are using NT, then the NT client 4. something or newer will work for single sign-in

Hope this helps

 

[DrGreen26]

Correction, that is the Novell Client for NT

and one other item:

if you do the 2 nic card thingy, then you might want to make sure you are not creating any loops in your network...this would be a bad thing. Secondly, I am not sure how microsoft does this, but with 2 nics, your pc may potentially act like a router, so do verify that before you do it.

 

[dpellegrini]

NT has a setting &quot;Enable IP Forwarding&quot; if this is checked, in the properties of TCP/IP, then your NT server can act as a router. Also if it inside the network, and you don't need it to access anything outside, on the web or through the router, then don't define a gateway. Accessing both NT and Novell from one PC can also be done by using Client32 for Novell, binding IPX to Novell's client 32, and then using Client for Microsoft Networks, with TCP/IP bound only to that, to attach to the NT server. Pretty much the same but different way to log into both. [sig][/sig]