JetDirect 300x Linux problems

[miclederer]

Hi, anybody ever came across this:
I have a JetDirect 300x print server (J3263A with latest firmware H.
08.60) that works perfectly when used from a Windows pc but refuses to
work when used with Linux. In particular I cannot connect from Linux
via telnet or ftp, while the same thing works from Windows (tested on
several pc's for both operating systems). Same is true for printing:
Windows OK, Linux denial of service. I have no idea where this comes
from, it doesn't seem to be connected to SELinux.

Help would be appreciated!

Michael

 

[Rev.GGWillikers]

Hi, anybody ever came across this:
I have a JetDirect 300x print server (J3263A with latest firmware H.
08.60) that works perfectly when used from a Windows pc but refuses to
work when used with Linux. In particular I cannot connect from Linux
via telnet or ftp, while the same thing works from Windows (tested on
several pc's for both operating systems). Same is true for printing:
Windows OK, Linux denial of service. I have no idea where this comes
from, it doesn't seem to be connected to SELinux.

Help would be appreciated!

Michael

Have you tried Webjat admin?

http://h20338.www2.hp.com/hpsub/cache/332262-0-0-225-121.html

 

[Warren Block]

Have you tried Webjat admin?

http://h20338.www2.hp.com/hpsub/cache/332262-0-0-225-121.html

Ideas:

Firewall on Linux system.

Routing problem.

Newer JetDirects have a TCP/IP access control table which looks like you
can allow ranges of addresses and presumably denies everything else.

To the OP: there are some details which would make this easier to
diagnose. IP addresses, error messages, whether the JD responds to even
a ping from the Linux system. (Please note that I killfile posts from
Google Groups [99% spam], but you can email me.)

 

[miclederer]

I wanted to, but looking at the system requirements I didn't install
it. Anyway, it seems to be far more than I need, configuration via
telnet should do in my opinion...

Ideas:

Firewall on Linux system.

Turned the firewall off, no success.

Routing problem.

Maybe, but where does a network non-expert start looking?

Newer JetDirects have a TCP/IP access control table which looks like you
can allow ranges of addresses and presumably denies everything else.

By default this feature is turned off. I tried also to allow certain
addresses, but it didn't work either.

To the OP: there are some details which would make this easier to
diagnose. IP addresses, error messages, whether the JD responds to even
a ping from the Linux system. (Please note that I killfile posts from
Google Groups [99% spam], but you can email me.)

Pinging works from both Windows and Linux machines. No problems here.
IP configuration is static, all machines are within the same network.
Telnet, FTP, Web connection works with no restrictions whatsoever from
Windows. But I cannot connect in either way from Linux machines. This
is what I find puzzling, as all these protocols are standardized (are
they?).

Telnet from Linux, for example, says:

Trying [IP address]...
(after one minute or so)
telnet: connect to address [IP address]: Connection timed out
telnet: Unable to connect to remote host: Connection timed out

Similar thing for FTP. As I said, I turned off the Linux firewall and
SELinux, but it didn't help.

What is even more funny (and an important hint, I guess, although I
forgot to mention it): When I disconnect the power from the JetDirect
and reconnect it, connection from Linux is possible for a few minutes.
Then it somehow dies down again. Another example: sending print jobs
to the server is not successful, but the disconnect-reconnect game
does the job here, too. After some time the connection is lost again:
no prints jobs possible, no connection via telnet etc. Somehow it
stalls, but I have absolutely no idea why. And I don't know where the
problem is: I don't think that there is something wrong with the
printer server, as all goes right from Windows. Network is also fine.
It must have something to do with Linux, I suppose (and it isn't
related to a certain distribution, I checked from several machines
with different distributions/versions).

Michael