Wireless JetDirect Box - Connectivity

September 22, 2010 at 06:37:40
Specs: Windows XP
Ive a JetDirect box (HP ew2500) I can Telnet to only from a wireless PC, wired nope (95% of the time).

When I say a wireless PC I mean, Wireless PC to an Access Point to switch to switch to Access point to JetDirect Box.

However sometimes it will work for both. Same AP same PCs.

It appears that the JetDirect box negotiates something when it joins that will stop/allow telnet (and browsing to embedded web server) from a wired PC.

Funny thing is, Ping works all the time for both Wired and Wireless PCs.

DHCP is all fine. Wireless security has been ruled out.

Ideas?


See More: Wireless JetDirect Box - Connectivity

Report •


#1
September 22, 2010 at 07:08:52
This sounds like a setting internal to the jetdirect. I've never played with a wireless one but if it were me, I'd grab the manual and connect to the management interface. I'd be looking to see that telnet, HTTP, and SNMP sessions were allowed to connect to it.

I know with the enterprise level switches I use here at work, only telnet is enabled by default on them and I have to manually enable HTTP and SNMP to be able to connect to them that way.

If I'm right and it's a simple case of enabling those types of connections, I'd give serious thought to disabling the ability to connect to it the management interface via wireless. That's a pretty big security issue in my mind. I would only allow wired connections to access the management interface.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#2
September 22, 2010 at 07:25:50
But thats the killer, they are enabled...
If im using a wireless PC, over the network I can Telnet fine.
Wireless PC - AP - Switch....Switch - AP - JD Box = OK

If Im using a Wired PC over the network, it fails, pretty much 95% of the time.
Wired PC - Switch....Switch - AP - JD Box = Not Ok

And I havent changed any settings.

If Disconnect/reconnect... its pot luck, like I said, most of the time a wired connection will fail, but sometimes Itll work.

I cant see why the Box should treat a wired/wireless PC differently... maddingly strange


Report •

#3
September 22, 2010 at 08:29:46
It shouldn't treat them differently.

Are the wireless network and the wired network on different subnets?

Are you using VLAN's?

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

Related Solutions

#4
September 22, 2010 at 08:32:46
Nope and nope.

Crazy isnt it?!

I still recon its something negotiated when the JetDirect box connects to an AP.

Its hardly packet size? Speed/handshake?...


Report •

#5
September 22, 2010 at 08:37:56
Cant be routing either, PING always works from wired and wireless.

If I Deauthorise the JD Box, there seems to be a small window of opportunity to telnet/browse on to it from a wired PC, before it automatically reauthorises and the connection is cut. Which is why I recon its a negotiated setting thats doing it.

We have created new SSID's with no security, these behave in the same way.
So its not a security issue.
Besides, if it was, it would affect wireless and wired PCs equally.


Report •

#6
September 22, 2010 at 08:56:08
the JetDirect box uses 802.11g
A quick google says thats half-duplex...

Im just wondering if this is somehow where things fall down.

Thing is, the wireless PC's use 802.11n, which is full - duplex...as a wired PC would be.


Report •

#7
September 22, 2010 at 12:30:05
I should have asked you earlier which it is you're trying to access........the printers management interface or the JetDirect's?

Regardless of which, I suspect you still have a setting disabled that's preventing the wired connection to whichever management interface. Check through your settings for 'remote management' settings and ensure they're all enabled.

The only other thing I can think of is maybe a setting in the AP's themselves preventing a wired telnet connection to the wireless JD.

Other than that, nothing else seems likely. You have no VLAN's. It's a single subnet and you can ping the device properly. This says clearly there is no physical (hardware) issue preventing the connection. Ergo, it must be a software issue.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#8
September 23, 2010 at 01:24:54
Yeah Im connecting to the embedded Web Server on the JetDirect.

I dont think its a setting per se. As in a tick box to allow....
otherwise it would deny access all the time. It doesnt. On rare occasions it does allow access.
So its not a setting thats hard and fast. Probably something set to Auto.

Telnet works, 100% of the time for a wireless PC. The only setting on the JetDirect box for Telnet is a blanket allow-deny.
There is no deny Telnet access to wired PCs, allow Telnet access to wireless...

We have two JetDirect boxes, both are the same in terms of this issue. So unless we are very unlucky, it isnt, as you say, a hardware issue.

Not sure if I mentioned - no new updates to firmware is available.


So, when everything else is equal, and its not a hard n fast setting, What negotiated setting allows a wireless PC to connect to a Jetdirect box (802.11g), but not a wired?
Cos its not only Telnet, but also browsing to it...


Report •

#9
September 23, 2010 at 07:38:30
Well, if I were in your shoes, I'd be calling the manufacturer right about now.

Sorry I couldn't be of more help.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#10
September 24, 2010 at 02:03:27
No worries, I'll get it sorted eventually. Thanks for your help!

Report •

Ask Question