We have an MFD (network printer) issue and it is a real doozy. There are 7 users in one office with a network printer. Only 4 of the users can print and ping the printer. The other 3 cannot print or ping the device. All 7 have network access, email, etc. They are all on the same VLAN and are connected to a 4507 in a Layer-2 setting. From the user's/printer switch we cannot ping the printer. However, we can ping the printer from the Router. And the printer IS connected to the network.
We have never had this type of issue before. Usually printer issues are due to incorrect IP settings or something simple... We do not know what the issue can be BUT, these are the only things we have found that it could possibly be.
When a show mac-address table is done we see the port for the printer with the protocols of dynamic, IP, IPX, other. But the users with the printer issue only have dynamic for their ports. (On a side note there are a whole slew of other ports with all of these same random protocols on them.) As far as we know there is not a need for multicast on our network so we do not know why there would be IPX and multicast commands on the network.
Also, when we enter our 6500's we attempt multicast commands and receive the reply that multicast is not currently running on the network. However, we have compared the 4507 configs with another 4507 config and we found multicast commands on the 4507 with the printer issue. After removing the multicast commands we do another sh mac-address table command and the IPX is missing from that port with the printer. BUT if we wait a minute and do another sh mac-address table command the IPX returns on its own. It's as if there is other multicast issues on the 4507 or our network that automatically renables it on that port.
Like I said, I don't know if IPX or multicast is the issue with the 3 users and the printer but this is the only reasoning that we can come up with. Hopefully my description isn't too confusing.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...