My Jetdirect print controllers are not accesible over Wi-Fi anymore. I believe this may be due to a recent code upgrade, but I'm unsure. A technichian made me aware that we are no longer able to search for devices on the internet. I'm under the impression some sort of filter is enabled, but I have no idea were to begin.
Was there an upgrade?
Were there any changes?
You need to give us something to go on...
The system was flashed by another engineer in June. Since then, no one can print to the wireless jetdirect devices/printers. Classes were out and we didn't get reports untill the end of August. I'm just now getting the news (bad news).
Old version: I have no idea.
DHCP: Yes (the jetdirect grabs a reserved address)
Add Printer Wizard in Windows will not find the device.
Print jobs will stay spooled and error out.
The clients might be using broadcasts to find the printers. Under the Virtual AP profile, you might want try turning off "Drop Broadcast and Multicast" under Configuration> Wireless> AP Configuration. Edit the AP group that your access points are in. Expand Wireless Lan. Expand Virtual AP. Click on the Virtual AP that your users are connected to. In the right pane, uncheck "Drop Broadcast and Multicast" and click on apply and see if it changes things.
According to our infrastructure engineer, we had tried that already and it did not work.
Well, alot of time has passed since June. We have to know what changes were made to your infrastructure for us to even have a hope of finding out why it does not work. You might start out by finding out from HP or Microsoft:
- What protocol is used for Windows devices to discover Jetdirect print servers?
- Do those clients need to be on the same subnet to discover those printers?
- What protocol is used for Windows devices to discover Jetdirect print servers? From above, we use TCP/IPv4 which is used for discovery.
- Do those clients need to be on the same subnet to discover those printers? Yes they need to be on the same subnet, and they are on the same subnet.
We were using captive portal, but that was disabled for testing. The reults were the same, and we could not discover the devices or print. I'm going to start a wireshark capture and attach it to a post.
I would like to note that one of our technichians stated that he was unable to view shared network devices (i.e. personal laptops, gaming devies, etc.) on public-wireless when the code change was made. The Jet-direct devices are on public wireless.
I'm unable to attach a wireshark capture.
One place that he can check is the general controller firewall settings:
Configuration> Advanced> Stateful Firewall.
Make sure that Deny Inter User Bridging, Deny Inter User Traffic are unchecked.
That has already been done.
I was able to get a TrendNet device setup to allow printing. When using the wireshark capture I saw:
Ping to the IP using IGMP protocol
Pulled up the properties of the printer and saw SNMP traffic
Setup a new printer and saw TCP traffic (ACK, PSH, FIN)
When trying to connect through the Aruba device, I didn't get any of this. We've also had problems with captive portal and connectivity with some devices, mainly handheld. Our Infrastructure engineer who works with the wireless set an open Group, and still nothing.
Like I said before, we didn't have problems untill the last upgrade. I've had no resolution and we've been down since the Summer.
I reported what I could to the Engineer in charge. Unfortunately access to the controller is locked down. If I'd been here for 15 years, they'd probably let me have more control.
I believe he'd been working with a tech from Aruba. The problem still exists. I'm thinking there must be some compatibility issue with the latest code upgrade, or some serious ignorance on the part of our engineer and the Aruba tech. I'm a brain with no body, it gets frustraiting having to help someone or ask for help, when no one can help.
I'm done, we can close this thread. There will not be a fix to this. If anyone is reading this and has success with an HP Jet direct device, please post something. Otherwise, I warn you all that there is not current fix for my issue, which is simple connectivity to a wireless jet-direct device (EW2500).
Anyone following this posting, there was a resolution by Aruba but not from this thread. Please find another thread that can help, this one is a dead end.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.