D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: ponders on December 21, 2008, 09:06:44 AM
-
I have a Ricoh Aficio SP C410DN printer connected via wire to the DIR-655. I have been unable to print to it ever since switching from an older Buffalo Wireless router to the DIR-655. This problem occurs whether the computer I'm printing from is wired or wireless. To help diagnose the problem I've run tcpdump from the computer side to watch the network traffic. As can be seen below, when attached to the DIR-655 the printer terminates the connection right after the computer sends the first real data in the conversation. Any idea what could be going on in the DIR-655 that would cause this difference in response from the printer?
--- Start of communication (all cases)
1- Computer sends SYN
2- Printer sends SYN (and ACKs the Computer's SYN)
3- Computer ACKs the Printer's SYN
4- Computer PUSHs, 2 bytes
5- Printer ACKs
---- Non-working case (DIR-655)
6- Printer sends FIN
7- Computer ACKs FIN
8- Computer sends FIN
9- Printer ACKs FIN
---- Working case (Buffalo)
6- Printer PUSHs, 1 byte
7- Computer ACKs
8- Computer PUSHs, 24 bytes
9- Printer ACKs
...
Thanks,
+ P:
-
IMHO your printer is the culprit and does not seem to return a push, 1 byte (step 6 working case/non working case) and sends a FIN , which is ofcourse ACK by the PC.
Any possibility to swich printer driver on your PC?
-
Ricoh seems to have rich driver support for many operating systems, nearly all of which have been updated in November & December 2008. Have you tried using some of those drivers instead (e.g. PCL6)?
Also, have you contacted Richo's support line to see if they have a more recent firmware image for the printer and/or printer nic? I couldn't find any on their support page, but oftentimes vendors release these on a per-request basis.
-
As it turns out I'm having problems printing from both Windows & Mac. The tcpdump above (in my first posting) is from the Mac. It may be worth looking for a driver update and/or printer firmware update (which I will do) but the key question for me is why would having the DIR-655 vs. a Buffalo WBR-G54 both acting only as a switch between the computer and the printer make a difference (i.e. why does it work for one and not the other)?
Thanks,
+ P:
-
What firmware are you running (with or without SecureSpot)?
-
As it turns out I'm having problems printing from both Windows & Mac. The tcpdump above (in my first posting) is from the Mac. It may be worth looking for a driver update and/or printer firmware update (which I will do) but the key question for me is why would having the DIR-655 vs. a Buffalo WBR-G54 both acting only as a switch between the computer and the printer make a difference (i.e. why does it work for one and not the other)?
Thanks,
+ P:
You could try different settings in the firewall department
-
I'm running the 1.21 firmware without SecureSpot. I haven't modified the advanced settings except for disabling UPnP so the firewall is using default settings. From the traffic shown in tcpdump the firewall is clearly allowing traffic between the computer & printer. It's conceivable that some kinds of traffic are being blocked there's nothing obvious in the settings to indicate this, nor is there any evidence of this in the tcpdump.
+ P:
-
I have a Ricoh Aficio SP C410DN printer connected via wire to the DIR-655. I have been unable to print to it ever since switching from an older Buffalo Wireless router to the DIR-655. This problem occurs whether the computer I'm printing from is wired or wireless. To help diagnose the problem I've run tcpdump from the computer side to watch the network traffic. As can be seen below, when attached to the DIR-655 the printer terminates the connection right after the computer sends the first real data in the conversation. Any idea what could be going on in the DIR-655 that would cause this difference in response from the printer?
--- Start of communication (all cases)
1- Computer sends SYN
2- Printer sends SYN (and ACKs the Computer's SYN)
3- Computer ACKs the Printer's SYN
4- Computer PUSHs, 2 bytes
5- Printer ACKs
---- Non-working case (DIR-655)
6- Printer sends FIN
7- Computer ACKs FIN
8- Computer sends FIN
9- Printer ACKs FIN
---- Working case (Buffalo)
6- Printer PUSHs, 1 byte
7- Computer ACKs
8- Computer PUSHs, 24 bytes
9- Printer ACKs
...
Thanks,
+ P:
Awesome description.
What TCP port is the printer answering here? (helps me ID the protocol)
Is there a delay, probably between packet 5 and 6 in the failing cases?
If the ports are 139, 445, and/or there is a delay, then see this -- Printing and LAN problems with DIR-firmware 1.2X (http://www.dslreports.com/forum/r21581163-Printing-and-LAN-problems-with-DIRfirmware-12X)
If that helps, it probably has more to do with the printer recognizing the printing station as a resource on the workgroup than the delay being discussed. The steps to fix would be the same, although the root cause is slightly different.
-
It's a network printer, so I read. Did you install the printer as a network printer or as a local USB printer (you can never tell...)? Possibly you've chosen the wrong protocol for the driver? Could you elaborate some more on the IP printer setup you have?
-
Is the securespot feature disabled?
-
Hi ponders,
You wrote "C410DN printer connected via wire to the DIR-655".
Is the printer plugged into the USB Port on the D-Link Router or is the printer plugged into the Ethernet Port on the D-Link Router?
-
With a little embarrassment I'm happy to report that I found the problem and have fixed it. It turned out, as I'd hoped, to be something simple and nothing (directly) to do with the DIR-655. My printer (a Ricoh Aficio SP C410dn) has an access control capability which causes it to drop requests from IP addresses outside specified ranges. I had forgotten that I had turned this access control on and it was set to filter to a pretty narrow range of addresses. When I set up the new DIR-655 I increased the range of IP addresses handed out by DHCP and since the DIR-655 DHCP server hands them out from highest to lowest it was handing out IP addresses outside the access controlled range allowed by the printer. Fixing the range on the printer to match the range handed out by DHCP solved the problem.
Thanks to everyone for their responses and reminding me that the problem could be with the printer despite the fact that it was the router that had been replaced.
+ P:
-
Thanks to everyone for their responses and reminding me that the problem could be with the printer despite the fact that it was the router that had been replaced.
Thanks for reporting back. Looking at the (ack/syn/fin) info you provided router error was more or less the only option....but glad you figured that out!
Happy holidays