Member Avatar for mrjaime

I have two networks setup. first 192.168.1.X Linksys router connected to WAN and second network 58.58.58.x 3com wireless both with DHCP with internet. My printer is located on a server in the first network with ip

I Can view any printer shared on first network, but when trying to connect to printer from second network can't see it.
I can ping address from with no lost.
How can I see shared printer in second network from first network?
Thank You ahead of time for any help.
Jaime

  • 3 Contributors
  • 2 Replies
  • 111 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by DimaYasny

Dani AI

Generated

— short diagnosis and practical steps.

Because the two networks are separate subnets, Windows' browse/name-discovery (broadcast-based protocols) will usually not show shares across the router; that matches 's point. That is a discovery problem, not necessarily a routing one, so direct IP-based access is the fastest workaround. Also confirm the printer is actually shared and permissions are correct, as suggested.

Try these steps in order:

  • Connect by IP/UNC first. On a Windows client use "Add a printer" -> "The printer that I want isn't listed" -> "Add a printer using a TCP/IP address or hostname", or open Explorer and enter the UNC path:

    \\SERVER_IP\PrinterShare

    If that succeeds, install the driver and keep the IP/TCP port.

  • If the direct connect fails, check the server's sharing and Windows Firewall rules. Allow only the other subnet to reach the server on the required ports (avoid opening SMB to the world). The important ports are SMB/NetBIOS (TCP 445, 139; UDP 137–138); IPP/LPR alternatives use TCP 631 and 515.

  • Example firewall rule pattern (replace placeholders):

    netsh advfirewall firewall add rule name="Allow SMB from OTHER_SUBNET" dir=in action=allow protocol=TCP localport=445 remoteip=OTHER_SUBNET_CIDR

Longer-term solutions: publish the printer via IPP/LPR on the device, add a DNS/WINS entry or hosts mapping for name resolution, create a route with narrow firewall rules between subnets, or move printers and clients onto the same VLAN. Avoid broad SMB exposure over routers or the Internet — prefer IPP or a secure tunnel for cross-subnet printing.

Checklist for troubleshooting: verify the share and NTFS permissions, confirm firewall exceptions for the specific subnet, test the UNC path, and test the required ports from a client.

Recommended Answers

All 2 Replies

Member Avatar for fayyaz

Hi
Have you share priunter ?

Member Avatar for DimaYasny

generally the printer might be working on different protocols. some protocols, like netbios, cannot pass routers.

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.