Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

We have a simple printer running a jetdirect service on 9100 listening for incoming characters. It is sits behind a modem that serves a static IP to a router. I can telnet in and print arbitrary characters. Oddly, the first connection takes much longer then the next one. I setup a script to continually ping the address every three minutes. When I attempt to connect after setting this script up the connection is, more or less, instantaneous. This might make sense if there was some sort of dynamic address resolution but I don't understand why it is working this way with a static IP. The connection is ADSL2+ through SureWest.

I'm sure it's something I'm overlooking. Please enlighten me.

share|improve this question
    
The initial description sounds a lot like a dns resolution timeout, then maybe caching of the failure makes it work. But I wouldn't expect a ping to trigger a lookup. In any case, does the printer have a dns server configured it can't connect too? –  Matt Feb 15 '13 at 1:05
    
I was expecting something similar, but this is using the SureWest network. I'm thinking it might be the case that they assign static addresses differently with some sort of caching layer perhaps.... –  Esoteric Feb 15 '13 at 16:40

1 Answer 1

Does the printer and/or JetDirect module sleep? If so it might take a few seconds to wake up.

share|improve this answer
    
Neither the printer nor the JetDirect module sleep. We have a couple hundred other of these printers deployed and this is the first time we are seeing this issue. –  Esoteric Feb 15 '13 at 16:13

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.