NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
PETERGATS
Mar 02, 2014Aspirant
Printing segregated to VLAN by itself
For the life of me, can't get the printer to be alive on its own VLAN.. The SRX5308 is the fw-router (no VPNs just VLANs) Identified 12 VLANs and treating these as port based VLANs and there's a M...
PETERGATS
Mar 03, 2014Aspirant
I have moved the printer back into the default LAN
Of course the default LAN prints fine to it and just checked the printer's IP, subnet and deflt gw and it gets these fine from dhcp on the SRX5308
But alas i have tried all i can think of on the SRX5308 and on the M4100 to get the VLANs to be able to see it and print to it. (so far zilch, from VLANs no ping backs )
I have tried a static route on the SRX5308 pointing right to it on the default LAN (VLAN 1)
I have tried VLAN routing on the M4100, but alas the M4100 (with latest fw) tells me no VLAN routing to the management interface LAN)
I could try moving the ip addr i get to the M4100 , howver if i did i'd have to get a laptop and plug right into it in order to configure it henceforth)
I have tried MAC based traffic control under security tab on the M4100, no go
I have tried some ACL, but here i tread lightly bcs i can lock up entire building with all its VLANs as i found out earlier, if i stipulate incorrect parameters in the ACL..
So, is it really this difficcult?? so as to be able to put in some "rules" to get the VLANs to print to a single printer on the default LAN?
SOmebody out there must have a shared printer shared amongst all their VLANs, how didja get it working?
I also have a case with Netgear L2 support, but so far nuthing fruitfull, so i am plugging away at this problem both on these forums and thru support, who have taken Teamviwer remote control of both inside (and outside machines, outside of the Building itself on the general internet), so far nuthing on that end, it's been like 5 days into this case now.. I am scratching my head thinking, it cannot be this difficult to share a printer amongst all these VLANs..
Pls remember that i cannot allow interVLAN routing, except for the default VLAN which has interVLAN routing enabled. All the other VLANs work fine but must stay segregated to their own traffic, so they wont be able to snoop each other's traffic or devices..
The internet works great on all VLANS and teh default LAN, both incoming and outgoing services (by incoming i am talking about firewall port fwd rules, so users can telecommute and such)
Having said all that, as far as the building itself is concerned, i can ping from any VLAN to the default LAN, but only the SRX5308 answers back as the default gw.
Any devices on teh default LAN do not answer back
Thsi is by design i think, so the printer now doesnt answer back either.
Teh reverse is also true on teh LAN, in that there is no pingbacks for any pings sent from teh default LAN to any of the VLAN ports.
Rememebr the M4100 is being used as a portbased VLAN switch, where any single port is equal to a single VLAN.
Anyways, pls keep advice coming.
TY
Of course the default LAN prints fine to it and just checked the printer's IP, subnet and deflt gw and it gets these fine from dhcp on the SRX5308
But alas i have tried all i can think of on the SRX5308 and on the M4100 to get the VLANs to be able to see it and print to it. (so far zilch, from VLANs no ping backs )
I have tried a static route on the SRX5308 pointing right to it on the default LAN (VLAN 1)
I have tried VLAN routing on the M4100, but alas the M4100 (with latest fw) tells me no VLAN routing to the management interface LAN)
I could try moving the ip addr i get to the M4100 , howver if i did i'd have to get a laptop and plug right into it in order to configure it henceforth)
I have tried MAC based traffic control under security tab on the M4100, no go
I have tried some ACL, but here i tread lightly bcs i can lock up entire building with all its VLANs as i found out earlier, if i stipulate incorrect parameters in the ACL..
So, is it really this difficcult?? so as to be able to put in some "rules" to get the VLANs to print to a single printer on the default LAN?
SOmebody out there must have a shared printer shared amongst all their VLANs, how didja get it working?
I also have a case with Netgear L2 support, but so far nuthing fruitfull, so i am plugging away at this problem both on these forums and thru support, who have taken Teamviwer remote control of both inside (and outside machines, outside of the Building itself on the general internet), so far nuthing on that end, it's been like 5 days into this case now.. I am scratching my head thinking, it cannot be this difficult to share a printer amongst all these VLANs..
Pls remember that i cannot allow interVLAN routing, except for the default VLAN which has interVLAN routing enabled. All the other VLANs work fine but must stay segregated to their own traffic, so they wont be able to snoop each other's traffic or devices..
The internet works great on all VLANS and teh default LAN, both incoming and outgoing services (by incoming i am talking about firewall port fwd rules, so users can telecommute and such)
Having said all that, as far as the building itself is concerned, i can ping from any VLAN to the default LAN, but only the SRX5308 answers back as the default gw.
Any devices on teh default LAN do not answer back
Thsi is by design i think, so the printer now doesnt answer back either.
Teh reverse is also true on teh LAN, in that there is no pingbacks for any pings sent from teh default LAN to any of the VLAN ports.
Rememebr the M4100 is being used as a portbased VLAN switch, where any single port is equal to a single VLAN.
Anyways, pls keep advice coming.
TY
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!