I have a Windows 2000 system with Dual NICs. One is a 3com 3C509 10 MB ISA card that uses DHCP, The other is a 3com 3C905B-TX 10/100 PCI card that uses a static IP of 192.168.10.1. The problem is that if I enable the 10/100 card I am no longer able to connect to our PROXY server via the 10 MB card. If I disable the 100 MB card no problems, But I lose my connections to my Process Control network (192.168.10.xxx). Any solutions as to how I should configure my IP settings, or should I be cahnging the routing table ?<br><br>Thanks in advance, <br><br>Marinus Mellaart<br><A HREF="mailto:marinus.mellaart@weyerhaeuser.com">marinus.mellaart@weyerhaeuser.com</A><br>Process Control Technician<br>Princeton, BC
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Dual NIC NT 2000 Professional
- Thread starter Marinus
- Start date
I pretty much have the same layout here. One NIC attached to our Corp network using DHCP and the other to my Deadnet using a static IP of 192.168.x.x. I have a router incorporated into my Deadnet with an IP of 192.168.0.8.<br><br>Both NIC's have a default gateway respectively. We also use MS Proxy Server. However, I can have both enabled without loss of connectivity to either network.<br><br>Do you know if the network of 192.168.x.x has been included in the LAT of the Proxy server? If not, Proxy Server my see it as an external address. You may be able to use some other private address that is included in the LAT to workaround the issue....<br><br><br>dxd
- Thread starter
- #3
My Proxy Server / Firewall is on the Corporate side of the network which I have no control. There is a local router, which given time, I might be able to convince the IT group to reconfigure to better accommodate the process control network. There is a trust relationship between the Process Control network and the Corporate network - That is the Process control Network TRUSTS the Corporate network but not vice versa. But what I am not sure about is whether the 192.168.10.xxx can pass through the router to get at the Proxy / Firewall server on the WAN. I do not want Internet access from the 192.168.10.xxx network, I want that to go through my DHCP assigned address. Please advise <br><br>TIA<br><br>Marinus Mellaart<br><A HREF="mailto:marinus.mellaart@weyerhaeuser.com">marinus.mellaart@weyerhaeuser.com</A><br>Process Control Technician<br>Princeton, BC<br>
Well, it is somehwat confusing to me as to the layout of your network. Please correct me if I misunderstood......<br><br> World <br> ¦<br>Corp network------------Router A<br> ¦ ¦<br> ¦ Process Control<br> ¦ ¦<br>Your machine--------------<br><br>You indicated that Process trusts Corp, so I must assume that these two networks are interconnected through another device outside of your box. As such, I would also assume that if the Process network is 192.168.x.x and it can be accessed through the Corp network, then the Corp network Routers (or whatever device is interconnecting them) must have this route in their tables.<br><br>How is access obtained to the Process network? Must you be physically attached to the 192.168.x segment or can you get to it from the Corp segment? <br><br>You may want to run TRACERT on a device in the Process network to see where it takes you. There can be several causes, possible routing conflicts, filters enabled on the routers, or as I said before, the configuration of the LAT (local address table) of the Proxy server or for that matter security. Proxy can be set up to deny access per IP.<br><br>Check out your route table....take a snapshot and include it in your next reply.....or email it to me><A HREF="mailto:dndavis@ev1.net">dndavis@ev1.net</A><br><br><br><br>dxd<br><br>
- Thread starter
- #5
My Network is as such :<br><br>NIC_1_3c509 -------->LAN----------------->WAN------------------->Proxy----->Internet<br> 155.130.15.xx 155.130.15.xxx 155.130.xxx.xxx<br> <br>NIC_2_3c905B-TX -------> LAN ----------------->Process Lan <br> 192.168.10.10 192.168.10.1 192.168.10.xxx<br><br>PCSERVER - 192.168.10.1 and 155.130.15.131<br>PCSERVER2 - 192.168.10.2 and 155.130.15.132<br>PCSERVER3 - 192.168.10.3 and 155.130.15.133<br><br>There is no physical connection between the Process control network and the Corporate network. I do not want Corporate to communicate with Process or vice versa with the exception of the three NT 4.0 servers (pcserver, pcserver2, pcserver3) which also have dual NICs.<br><br>TIA<br><br>Marinus Mellaart<br><A HREF="mailto:marinus.mellaart@weyerhaeuser.com">marinus.mellaart@weyerhaeuser.com</A><br>Process Control Technician<br>Princeton, BC<br>
- Status