Connecting to 2 networks

[Jazza]

I have 2 networks in my office, as my company mergered with another one recently, and we haven't mergered the networks as yet. I was wondering what would be the best way for me to connect to them both networks.

I have tried 2 network cards, but that didn't work :(

Any suggestions?

Cheers

[Rmage]

In theory if you have a nt 4 or higher machine with 2 network cards you can add routing entries on the system to connect the 2.
Now I had a real bitch getting this working between ethernet and token ring I had to alter transmission sizes etc.

The other easier method is to buy a cisco bridge/router, but that will set your company back between £2500 and £5000 depending on network types.

I hate to say it but PC world business direct have a fair listing of Cisco kit. www.pcwbd.com

Hope this helps

[MONK]

Sorry no experience but I do know Rmage is right you could add routing to NT server. You could right you're own IP tables for linux with out to many problems.

Of course u if want to go with some spending I would go with a little router. Not sure what the advantages are cos you may be able to make a very system with a puter so hopefully someone with skills will answer :D

[zhardoum]

Big Hammer small nut time.

Before we all go running off cheque books in hand, can we stop and think a second first.

He has two networks in the office, ok so far.

wheres the problem, just hook the switches together, the question is he needs to know wether they are both Microsoft based, or is one Novell or unix or other.

Then get to nitty gritty level and work out subnets and ip ranges and is it dhcp and how about dns? and domain logons>

Then it is more a matter of network config rather than needing much else.

I advise finding out as much info about the current systems as possible, then let us know, and we will be in a far better position to tell you what to do.

it could in theory even be that 1 net is microsft and the other novell, in which it would be so easy its laughable.

I believe wizzo is looking for work in this area, fling him an email, he will be only too glad to visit and solve this for you as a consultancy job :)

[Jazza]

I'm not worried about the long time, as that is some one else's problem. I'm just trying to get my PC connected to both networks.

The network I'm currently connected to is Unix based, and the other one is an NT domain, which has VPN to our other offices, which is what I'm trying to connect to. The Unix network has real IP addresses, and the other 192.168.*.*

I'm currently running Win2k.

It's not that important, but I'm sure it must be possible.

[zhardoum]

more than possible in fact, its how 99% of companies work!

Ok, what you need to do is
connect both networks together by some fashion, usually taking a link from a switch and either using a crossover cable or normal to the uplink port on the other network switch, is then make sure that you can ping both domain server, for the Unix one you may need to change your ip address, the idea is then to make sure you can see both network allbeit at ping level only at first.

then, lets say you configure your pc for the NT side of things, and its all happy, what you then need to do, is configure a unix interface, either by using the Win2k add in, but then, you will more than likely need to add the route into hosts and services file, and dont forget the ADD ROUTE command to filter ip requests for the different subnet!.

It is quite straightforward this, if my memmory serves me right, it is just a question of making sure you add the ip and subnet of the unix domain into your hosts and services files, with the name of the server for dns use, and then add in a route command to set the path for for machine to know where the IP address of the unix box is, that way when you ping by name, the hosts table tell it what ip address the Unix server is at, the route file (most people add this as a *.bat into startup) then tell it how to access that IP address by using the IP route you have added.

That will allow you then to configure your Win2k unix client, to logon to the unix domain, and voila you then have 2 different domains via 1 cable to your machine.

There are other alternatives, special unix interface clients (ANITA for one) which basically just simplify the process for you by setting up a routing bridge within itself, so you end up with an icon on your desktop, click it, it then launches the ip bridge app, which routes you to the unix box.

If my memmory serves me right there is lots of different products like this, pc rhumba is one for example, or reflections is another, any way there is lots, and this problem is quite atraightforward, you wont need to layout much cash, only if you want a pretty terminal emulator program rather than messing about with hosts and services and routing scripts,

let me know if you need more help!

[Jazza]

Cheers for the info.

Shall let you know how I get on :)

[zhardoum]

Woke up last night at some god awful time and screamed 'oh yeah dont forget..'

You need to speak to the UNIX bods, make sure they have vision FS loaded, and make sure that they have the latest version.

Version FS is not as standard included in the unixware 7.10 or 7.11 installation, but it is an option on one of the CD's

VisionFS broadcasts the Unix ware domain onto NT level network browsing, so the unixware tree can be browsed using the NT explorer, even down to folders etc etc..

Make sure you load the Unix server client as well, you can remotley log into the unix server, and set up file access rights, user logon rights and scripts, all the jazz, really excellent tool

But dont be tempted to use webtop, it sucks and the java takes way to long to load and 9 times out of 10 doesnt.

only fault with vision FS is it broadcasts in to all NT domains and subdmains and workgroups, so everyone in the entire compnay will see it, they cant access it but you will get 101 questions like what is it, why it there etc etc, amazing tool but a pian as its either on or off and cant be limited to certain sections of the NT domains..

I suggest that you get your head together with the Unix peeps you have and sort it between you, they probably would be interested in helping you to each others benefit.

Hope that helped