I have two separate network segments, both segments use Linksys routers. Segment A feeds the router for segment B (separate/different IP schemes). One XP machine on segment B would like to use a networked/IP addressable printer on segment A. I am going to install a 2nd NIC into the XP machine on segment B and assign it a static IP address from segment A. Other than installing the printer driver with the appropriate printer IP on the XP machine is there anything else I will need to do?

The only needed access on segment A is just for the IP printer. Segment B is used for the internet, file sharing, VOIP, etc. for the XP machine. What other configuration will I have to do so XP doesn't try to use segment A for internet access etc. It seems like there would be some confusion within XP as to what IP/NIC it will use for what task.

Thanks, Jim

Dani AI

Generated

— Short answer: yes, a second NIC will work, but a few configuration details will keep Windows from “choosing” the wrong network for Internet traffic.

Do this first: give the new NIC a static IP from the printer network and do not enter a default gateway on that interface. Leave the default gateway (and primary DNS) only on the NIC that should handle Internet access. If the printer is addressed by name, add a hosts file entry pointing the printer name to its IP so name lookups don’t go out the wrong DNS server.

A couple of practical tweaks:

  • Set explicit interface metrics so the Internet NIC has higher priority (lower metric) and the printer NIC has a lower priority (higher metric). In XP this is under the IPv4 Advanced settings.
  • Don’t try to “merge” the two networks by changing the printer’s subnet mask to a larger mask — that causes routing and ARP problems and is not the right fix.
  • If you still have trouble reaching the printer, add a persistent route on the PC that pins the printer’s IP to the second NIC’s interface, or put a static route on one of the routers so the two segments are routed properly.

Troubleshooting checklist: ping the printer IP from the machine after the NIC is up, verify the PC’s routing table, check the Windows firewall and Linksys settings (no ICS enabled on the printer NIC), and confirm there are no IP conflicts. If the printer needs Internet access for updates, give it a gateway on its own network; the PC does not need one on that NIC.

I have two separate network segments, both segments use Linksys routers. Segment A feeds the router for segment B (separate/different IP schemes). One XP machine on segment B would like to use a networked/IP addressable printer on segment A. I am going to install a 2nd NIC into the XP machine on segment B and assign it a static IP address from segment A. Other than installing the printer driver with the appropriate printer IP on the XP machine is there anything else I will need to do?

The only needed access on segment A is just for the IP printer. Segment B is used for the internet, file sharing, VOIP, etc. for the XP machine. What other configuration will I have to do so XP doesn't try to use segment A for internet access etc. It seems like there would be some confusion within XP as to what IP/NIC it will use for what task.

Thanks, Jim

Sorry for the confusion I'm new!!!
Here's what I have.

Segment A
Gateway DHCP on
Subnet
Shared Printer

Segment B
Gateway Router DHCP on
Subnet

I'm putting a second network card in a CPU on Segment B to access Segment A's Printer.
Both Segments have their own internet access and are in the same office.

1st NIC (existing) IP (seg B)
Subnet
Default Gatway
DNS Server

2nd NIC (new) IP (seg A)
Subnet
Default Gateway
DNS Server

How does all of this look, I think I need to change the Subnet on the Printer:
Printer IP
Subnet (current)
Subnet (new)

I will manually assign the IP/Subnet/Gateway/DNS for the two network cards in the system.
My only confusion is the Subnets do they look correct? I only want to access Seg. A for the printer.

Thanks for the patience!!

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.