jakechaffee
Technical User
I'll try to describe this simple. We have a large network that contains quit a bit of label printers. We recently ran into a issue where we needed a label printer out of the way and tried to use a wireless print server. No go when configured with the jet direct. It had to be hardwired because the jet direct did not like how the label handled its raw prints on port 9100.
Well the issue has arisen again and this time hardwired is out of the question so we are trying to set it up with a Linksys wireless bridge receiving from cisco aironet AP. Everything is cnfigured fine on the label printer (172.50.203.78) and the bridge (172.50.200.165).
Now the confusing part to us in Alabama. We have a sister company in Texas which is on a different domain that we have trust with and then a another company in Ohio that is in same domain. Both connected with dedicated t1 lines.
If the printer is pinged from Texas request times out EVERY time. If it is pinged from Ohio it can be seen. If it is pinged from here it can be seen. We can test print to it from here in Alabama outside of the program we need it for, but inside the program (SAP) we can not print to it. SAP is the program that requires the RAW print on port 9100 for the barcodes and labels. We're not sure if the problem is the bridge or if because of the travel time from Texas and the wireless that it is timing out way ahead of getting here.
Has anyone encountered anything like this before?
Jake Chaffee
"There are 10 types of people in the world. Those who can read binary and those who can't."
Well the issue has arisen again and this time hardwired is out of the question so we are trying to set it up with a Linksys wireless bridge receiving from cisco aironet AP. Everything is cnfigured fine on the label printer (172.50.203.78) and the bridge (172.50.200.165).
Now the confusing part to us in Alabama. We have a sister company in Texas which is on a different domain that we have trust with and then a another company in Ohio that is in same domain. Both connected with dedicated t1 lines.
If the printer is pinged from Texas request times out EVERY time. If it is pinged from Ohio it can be seen. If it is pinged from here it can be seen. We can test print to it from here in Alabama outside of the program we need it for, but inside the program (SAP) we can not print to it. SAP is the program that requires the RAW print on port 9100 for the barcodes and labels. We're not sure if the problem is the bridge or if because of the travel time from Texas and the wireless that it is timing out way ahead of getting here.
Has anyone encountered anything like this before?
Jake Chaffee
"There are 10 types of people in the world. Those who can read binary and those who can't."