[Last Call] Learn how to a build a cloud-first strategyRegister Now


Accessing two separate networks with one XP client

Posted on 2005-04-06
Medium Priority
Last Modified: 2010-04-10
I have a client who is running two seperate networks. One is running through a 10MPS hub and handles automotive parts and billing. It has it's own set of defined IP addresses and Subnet.

The other network is running over a 10/100 hub. This network will soon have Windows Server 2003 on it with specific automotive software installed.

Both networks terminate in one room with both hubs on a rack

All machines throughout the network are Windows XP Professional.

What I need to be able to do is access both networks from any machine so that the accounting department can run the software that is installed on either network.
Question by:DougJonsen
LVL 25

Expert Comment

ID: 13719875
are the networks connected phyically at all?
what is the IP address scheme of each network?

Expert Comment

ID: 13720092
You could run a crossover cable (or patch cable via an uplink port on either hub) and connect the 2 hubs together, then give the accounting department computers multiple IP addresses (one address & netmask for each network...in network TCP/IP properties, advanced, then add).

This may generate too much traffic on the 10mbit hub, depending on your specific environment but other than that I can't think offhand of a reason this wouldn't work.  

I've done something similar on an XP box at home for about a month when I had overlapping service during an upgrade from SDSL to a T1...had to send an .iso to a friend on 3mbit cable so I plugged the T1 router and SDSL router both to the same 10mbit hub, gave doze an IP/netmask on each subnet, and had him ftp in twice simultaneously...once through it's SDSL IP and once through it's T1 IP, he was able to suck the whole 1.1 + 1.544 mbit upstream I could dish out.  I've also done quick-n-dirty hardware protection using this method...needed to protect our phone system on the LAN since it had a tendency to drop calls when things like an NMAP scan was run locally and it hit the phone system...I just couldn't get people to remember to exclude it's IP from their playing around so I put the phone sys on a different subnet then added (in addition to their original ip/mask) an IP on the phone system's subnet to the 2 computers that needed occasional access to the phone sys.

Accepted Solution

salvagbf earned 375 total points
ID: 13720309
"What I need to be able to do is access both networks from any machine"

Then you should probably just take the time to make a single network.  If you say both networks are each on their own hub, that can't be a huge network.  So long as you have fewer than 254 computers, just join one subnet to the other.

My guess is that each network is on a different 192.168 subnet right? Just put one network's worth of machines on the other subnet (by changing their IP address) and join your hubs with a crossover cable.  Done deal.

A Cyber Security RX to Protect Your Organization

Join us on December 13th for a webinar to learn how medical providers can defend against malware with a cyber security "Rx" that supports a healthy technology adoption plan for every healthcare organization.


Expert Comment

ID: 13720978
True enough...one subnet for all would work, although  I interpreted "..from any machine so that the accounting department can run the software that is installed on either network." as implying that the two existing networks were separated for other reasons, hence the suggestion for multiple IP's on the accounting machines (which could be scattered accross both networks).

Bernie interpreted the question literally, I made an assumption based on the ebb & flow of the rest of the message.  

Meanwhile, Mike simply asked for clarification first (prolly the safest route!)

Gotta love seeing in action different methods to approach problem solving...what a boring planet this would be if we all thought the same way :).

Expert Comment

ID: 13721001
One (probably obvious) sidenote...if the two physically separated networks are using the same subnet, then either one of them would have to be changed (to maintain separation of the two networks) or individual conflicting IP's changed (if any) if making one big subnet for everything was appropriate once the two hubs were linked together.

Expert Comment

ID: 13723810
well..this is a windows network...Do you have a domain controller (Directory server) or a workgroup?

Eitherway you could route...put a common machine in the middle (windows 2003 server will do it).......and use it to route...

off course, besides the Ip routing issue, you will also have the security issues.

Provide more details, as far as network topology.

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

Question has a verified solution.

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

This month, Experts Exchange’s free Course of the Month is focused on CompTIA IT Fundamentals.
LinkedIn blogging is great for networking, building up an audience, and expanding your influence as well. However, if you want to achieve these results, you need to work really hard to make your post worth liking and sharing. Here are 4 tips that ca…
Viewers will learn how to connect to a wireless network using the network security key. They will also learn how to access the IP address and DNS server for connections that must be done manually. After setting up a router, find the network security…
Internet Business Fax to Email Made Easy - With  eFax Corporate (http://www.enterprise.efax.com), you'll receive a dedicated online fax number, which is used the same way as a typical analog fax number. You'll receive secure faxes in your email, f…

831 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