Simply add an IP to your NIC with the servers range and you will be fine
I understand that the server should not have 2 NICs, but Ok if you assign your machine 2 IPs
Main Topics
Browse All TopicsWe have a media server (running xp pro) on 2.0.0.6 controlling a host of projectors and lighting on this network. Subnet is 255.255.255.0
We also have a regular network on 192.168.100.x, subnet 255.255.255.0 - Can anyone help in linking the two so that a computer on the 192 network can ping/RDP into the machine on the 2 network?
The server is connected to its own hub, and we have connected the hub to a port on our main switch. I have tried pinging but no response either way.
There's only one NIC and we were advised against adding another as the company that set the server up said if there were two NICs, the lighting control software wouldn't know which NIC to send the controls over.
I thought about adding a route using the route command but I have no idea at all what to type
Can anyone help?
Thanks!
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Thanks for that - it makes everything a lot clearer.
The reason its on the 2.0.0.0 is apparently the lighting network will not work on anything other than that.
So instead of using a hub, I need to buy a router, set it to have the 2.0.0.1 or whatever, then it can route through that if the routers "external IP" is one on the 192.168.100x lan
I guess I can try adding another IP, see what happens! I had no idea you could do that - learnt something new today!
If they're on the same physical network, if you add a second IP to any system on the 192.168.100.x that is on the 2.0.0.x network, it should work just fine. Alternately, if you want to add a second IP to the NIC on the server on the 2.0.0.x network (which should be fine), you'll be able to access via that IP and, if the 192 network's IPs are DHCP, you won't have to make anything static.
Also, if both network are sharing a router/firewall, you can create rules in that device to allow traffic between the two networks to communicate. It's the way that I use to allow traffic between my phone system network and data network.
Business Accounts
Answer for Membership
by: bjornlundePosted on 2009-11-04 at 04:02:07ID: 25738436
As I understand your setup:
ki/Private _network
- XP Pro media server on IP 2.0.0.6 with subnet mask 255.255.255.0
- Regular subnet is 192.168.100.0 with subnet mask 255.255.255.0
- There is no router between the two
To enable hosts on 192.168.100.0 to communicate with the host on 2.0.0.6 you would need to either set up a router between the two networks OR add an additional IP to the existing NIC which would have to be on the 192.168.100.0 network. Hosts on the 192.168.100.0 subnet would then be able to communicate with the media machine on that IP. I'm guessing, however, that the lightning control software will not be able to cope with that.
There is no way of enabling hosts on 192.168.100.0 to communicate with a host on a different network without a router because this is how IP is designed. A host on a network will always direct traffic to another subnet through its router (either default gateway or another router which routes to the 2.0.0.0 network).
I'm guessing that you already have a router in place which acts as your default gateway (e.g routes to the internet). When you ping from either host the packets are now sendt to this router, which tries to forward them to the internet. You can confirm this by running 'tracert 2.0.0.6' from one of the clients and from the media server. This will show you the path packets are actually taking.
If you were to connect the media server to a free LAN port on your existing default gateway router, and configure the the gateway router with an address on the 2.0.0.0 network (e.g 2.0.0.254) and then set up the media controller pc to use this IP as its default gateway you should be able to communicate with the server from your main network.
Also note that it is consiered best practice to use one of the reserved private ranges for internal IP addresses (e.g 10.0.0.0 /8 or 192.168.0.0/24 - 192.168.255.0/24) . The one you have set up is not a private address and is ment to be used as an external IP on the internet (currently listet as not allocated by IANA - but will be allocated to internet registries in the future). This could cause routing woes down the line.
Further reading on private ranges:
http://en.wikipedia.org/wi
Hope this helps
Bjorn