cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3374
Views
2
Helpful
19
Replies

mini printer vlan problem

Aquiles
Frequent Visitor
Frequent Visitor

i have a cisco switch with 4 vlans, i have a printer on native vlan and it can be ping, but when we send to print it just stuck on the queue on the computer,   but it respond to ping, but if we move to another vlan not native i cant even ping,  im using switch sf300-24pp small bussisness, what can i be missing.

19 Replies 19

Mark Elsen
Hall of Fame
Hall of Fame

 

  - For starters , check  - indeed if the printer can work if both the client (requesting a print) and the printer ; are in the same
    VLAN

 M.



-- Let everything happen to you  
       Beauty and terror
      Just keep going    
       No feeling is final
Reiner Maria Rilke (1899)

of course  they are in the same vlan,

Hi @Aquiles 

"i have a cisco switch with 4 vlans, i have a printer on native vlan and it can be ping, but when we send to print it just stuck on the queue on the computer"

 Meaning, connectivity is fine. The print stuck in the queue can be a computer problem.

" but it respond to ping, but if we move to another vlan not native i cant even ping, im using switch sf300-24pp small bussisness, what can i be missing."

 But did you move both PC and Printer to the same vlan? If not, they will not ping and this is the expected behavior.

 

 

 

yes they are on the same vlan vlan id 50, but somehow the printer doesnt seems to get even an ip address from dhcp, but if i move to native vlan the printer can get the ping

 

 - If the printer is not in the same vlan as the DHCP server  then you need to define  a DHCP relay for that vlan in the switch configuration pointing to the DHCP server ,

 M.



-- Let everything happen to you  
       Beauty and terror
      Just keep going    
       No feeling is final
Reiner Maria Rilke (1899)

But where are the DHCP server? Also in vlan 50? 

Keep in mind that if you mix up Vlans you need to have a layer 3 device or your switch need to support inter-vlan routing.

yes i have a dhcp server for each vlan

 

             >...yes i have a dhcp server for each vlan
  - Does that mean that you have several dhcp servers ?

  M.



-- Let everything happen to you  
       Beauty and terror
      Just keep going    
       No feeling is final
Reiner Maria Rilke (1899)

i have a each dhcp for each vlan

 

  - Ok  , let's backtrack a bit on the problem : if the host and  printer are in the same vlan , and you can ping the printer from the printer-client (needs a print) , can you then use and or print on the printer ?

 M.



-- Let everything happen to you  
       Beauty and terror
      Just keep going    
       No feeling is final
Reiner Maria Rilke (1899)

if the printer its on native vlan can be pinged, but if i vlan tag i cant, even if the client its on the same vlan, looks like the switch block the transmision for this device

 

   - Lets stay simple : when on same vlan  , no tags involved : can you then print ?

  M.



-- Let everything happen to you  
       Beauty and terror
      Just keep going    
       No feeling is final
Reiner Maria Rilke (1899)

i can ping but cant print, its wierd, if i tag , i cant even ping.

Then you problem is more likely with how you have setup the printer on the PC.

If you configure the printer with a static IP address and then manually setup the printer with that IP address on the PC does it work?

By default printers tend to rely on mDNS (Bonjour) to advertise their services and allow PCs to discover them.  If something on your switch is blocking multicast/mDNS then that will prevent autodiscovery of the printer.  If the printer is on a different VLAN from the PC then mDNS will only work with an mDNS gateway (mDNS is only designed to work on local layer 2 subnet/vlan by default)

------------------------------
Please click Helpful if this post helped you and Accept as Solution (drop down menu at top right of this reply) if this answered your query.
------------------------------
TAC recommended codes for AireOS WLC's   and   TAC recommended codes for 9800 WLC's
Best Practices for AireOS WLC's,   Best Practices for 9800 WLC's   and   Cisco Wireless compatibility matrix
Check your 9800 WLC config with Wireless Config Analyzer using "show tech wireless" output or "config paging disable" then "show run-config" output on AireOS and use Wireless Debug Analyzer to analyze your WLC client debugs
Field Notice: FN63942 APs and WLCs Fail to Create CAPWAP Connections Due to Certificate Expiration
Field Notice: FN72424 Later Versions of WiFi 6 APs Fail to Join WLC - Software Upgrade Required
Field Notice: FN72524 IOS APs stuck in downloading state after 4 Dec 2022 due to Certificate Expired
- Fixed in 8.10.196.0, latest 9800 releases, 8.5.182.12 (8.5.182.13 for 3504) and 8.5.182.109 (IRCM, 8.5.182.111 for 3504)
Field Notice: FN70479 AP Fails to Join or Joins with 1 Radio due to Country Mismatch, RMA needed
Field Notice: FN74383 APs Running 17.12.4/5/6/6a May Run Out of Flash Space Preventing Upgrades
How to avoid boot loop due to corrupted image on Wave 2 and Catalyst 11ax Access Points (CSCvx32806)
Field Notice: FN74035 - Wave2 APs DFS May Not Detect Radar After Channel Availability Check Time
Leo's list of bugs affecting 2800/3800/4800/1560 APs
Default AP console baud rate from 17.12.x is 115200 - introduced by CSCwe88390