[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1062
  • Last Modified:

Printing across VLANS

Core Switch HP5406 connected to 10 closet switches via fiber, closet switches mostly Cisco 3550, 2 HP (4204 and 2920)

VLAN 1 192.168.40.x  VLAN50 192.168.50.x Cisco Firewall 192.168.40.1

VLAN1 GW 40.2 (HP core Switch) VLAN50 GW 50.1 (VLAN IP on HP Core Switch)

Having issues getting clients on VLAN50 to print to printers on VLAN 1 40.x. I can ping 2 printers located 40.x, from VLAN50 but cannot reach another 8 printers.

Other services work across VLANS - Internet access, RDP to hosts, but others don't.

Should all closet switches have GW of core switch 40.2?

Not sure what else I need to configure.
0
MylesDRecon
Asked:
MylesDRecon
  • 5
  • 3
1 Solution
 
SuperiorCabinetsCommented:
Are you printing direct to an IP Address? Are you Printing through a print server? Are you using DNS Names for the printer address?
0
 
MylesDReconAuthor Commented:
Printing direct to an IP address. No print servers currently on network. A mix of windows and OSX clients only windows users are connected to AD. Using IP, not DNS to connect.
0
 
SuperiorCabinetsCommented:
Doesn't get much simpler than that!

When you connect to the Internet, does that route through to a different vlan as well?

I have seen some older printers that, even though you can set a default gateway, still no not actually route packets through the gateway.

What models of printers are you having issues with?
0
Transaction-level recovery for Oracle database

Veeam Explore for Oracle delivers low RTOs and RPOs with agentless transaction log backup and transaction-level recovery of Oracle databases. You can restore the database to a precise point in time, even to a specific transaction.

 
MylesDReconAuthor Commented:
Internet Access
40.x client - direct through Firewall 40.1
50.x client (VLAN50) - hits VLAN50 default gateway 50.1 which route to 40.1 firewall and fw routes back.

Printer Xerorx ColorQube and Xerox 3250 all have 40.2  as gateway
0
 
SuperiorCabinetsCommented:
What does the trace route look like from the clients on VLAN 50.x to the printers on VLAN 40.x?
0
 
MylesDReconAuthor Commented:
I have printers behind 4 of the 10 switch closets working.

From working areas trace - 192.168.50.1 -- (VLAN Gateway on Core Switch) -- printer IP
Non working areas trace drops out after 192.168.50.1 (VLAN Gateway Switch)

Of the 4 switches working (meaning 2 printers behind that switch work) 2 are HP switches and 2 are Cisco.

I need to check the IP config of the Cisco switches now, specifically Gateway, maybe they don't have the 192.168.40.2 (core switch) gateway defined.
0
 
choywaikinCommented:
I am guessing if the firewall block your print job, check which port number using for the printers.
0
 
MylesDReconAuthor Commented:
I'll check again, but I don't see any deny on the Cisco ASA, and I would think the traffic should all be local to the LAN, since all the gateways are set to the core switch.
0
 
MylesDReconAuthor Commented:
I added a global IP rule from 40.x to 50.x and it solved the issue Still weird since both networks are treated as inside at the firewall.
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now