Gateway between Win2k Network and Novell

GeekDrew

Diamond Member
Jun 7, 2000
9,099
19
81
My company has a Novell building server, to which all of our computers are connected for internet, file sharing, etc. The department that I work in needs to have its own Windows 2000 server-based network.

Right now we have 25 PCs that are all connected to a hub that connects it to the building Novell server. Is it possible to instead connect all 25 PCs to a Windows 2000 server and then install another NIC in the 2k server and connect it to the Novell server?

What I need to have is the Windows 2000 server maintaining all fileserving, etc, controlling everything, with the following exceptions. I have to let the clients authenticate to the Novell server and start Novell client trust, because the company uses BorderManager, which apparently relies upon that. The clients also need read/write access to their personal network shares on the Novell server.

This seems nearly impossible to me, but that's what I've been presented with. Is it possible at all?

Thanks!
Andrew (aka ST)
 

spidey07

No Lifer
Aug 4, 2000
65,469
5
76
NT and 2000 servers have a built-in tool called Gateway Services for NetWare that will do exactly what you wish.

Haven't used it in a while but do a search on MS technet for GSNW and you should find out all you need. The 2000 server will kind of "proxy" all netware connections. This way you can run a single MS client on the PCs.

Or you could just run both netware and MS clients on the PCs.
 

GeekDrew

Diamond Member
Jun 7, 2000
9,099
19
81
Hmmm... I have NetWare Gateway services installed, but I must be doing something wrong, since it's not working.

I can log in to the Novell server at the Win2k server console, but then nothing happens. I have to manually start Novell Client Trust from a drive that I manually map to the server. Then I start internet explorer, but it never does get around to contacting the proxy server. We have an intranet here also, and it can't locate that either. It's almost as though it is looking at the wrong network for the TCP/IP communication for the internet/intranet, etc.

Any ideas?

Thanks!
Andrew