jekarolchik
IS-IT--Management
I have a LJ 4000N printing on my TCP/IP network. The network is comprised of Sun Solaris and Windows NT computers which all connect to a Cisco Catalyst 6500 switch. All of the network addresses (including the printer address) are 7.160.32.x. The printer works fine from any node on the network.
Recently, we have been developing a multicast application which sends messages to a 239.x.x.x limited scope address. Other nodes that are interested read the multicast message from that address.
What we've noticed is that the LJ 4000N starts registering transmit collision errors as soon as the multicast server is started. This interrupts all print jobs until the multicast server is killed. I have disabled gmrp and broadcast to the printer port on the switch and also set ttl-sdp to -1 to turn off sdp on the printer.
Does anyone have an idea of what causes this problem and how to remedy it?
Thanks!
-j
Recently, we have been developing a multicast application which sends messages to a 239.x.x.x limited scope address. Other nodes that are interested read the multicast message from that address.
What we've noticed is that the LJ 4000N starts registering transmit collision errors as soon as the multicast server is started. This interrupts all print jobs until the multicast server is killed. I have disabled gmrp and broadcast to the printer port on the switch and also set ttl-sdp to -1 to turn off sdp on the printer.
Does anyone have an idea of what causes this problem and how to remedy it?
Thanks!
-j