Adding a router to a corporate network to create a subnet

PeterSmithson

Distinguished
Oct 7, 2011
1
0
18,510
Hi,

I'm in an office with a corporate network. I want to try out something to see if it will work generally at customer sites. The problems I have here is that I don't know much about networks and I don't know anything about the corporate network and have no access to it. If I need access to the corporate networks config to do what I want then please let me know as I then know I can't go further!

I have 2 servers that I want to run on a PC (Windows 7). The servers require a particular port number and want to connect to another device on the network at the same time. That won't work with just one NIC so I need two NIC's (or a virtual PC - that does work but isn't the solution I want to use). Two NIC's on the same network causes problems - it doesn't quite work.

I have a router (Netgear FVS318) and have plugged that into the corporate network (10.158.72.*). NIC 2 is plugged into that router and get's an IP address 192.168.1.2. For now, I disable NIC 1 (which would be connected to 10.158.72.*). I can ping my device and I get a reply - great. But when I try to use our proprietry protocol using UDP, I can see the packets go out to the device but the replies from the device do not make it to the PC (according to wireshark).

If I enable NIC 1, I get the replies coming through on that!

So that's the first problem, it can't seem to send the replies back through the router.

Secondly, even if I get that working, the device needs to be able to initiate requests to 192.168.1.2 which is (I believe) a whole different problem. How will the coroproate network know to route to my router for those addresses?

Sorry it's a big vague. Really, can I just add a router to an existing network like this quite easily?

Thanks.

Peter.
 
Solution
The new router's outputs can all talk to each other - read and write. And they can all listen (read) the input. But they can't talk (write) to the input. If the new router input is the only link you've got from the corporate router, then you can't send info from the new router to the corporate router unless the new router is a recognised device on the corporate network
The new router's outputs can all talk to each other - read and write. And they can all listen (read) the input. But they can't talk (write) to the input. If the new router input is the only link you've got from the corporate router, then you can't send info from the new router to the corporate router unless the new router is a recognised device on the corporate network
 
Solution