How can I set this printer up on a Static IP address that can be used over a WAN?

To confirm:  

Do the remote clients connect to your network using a VPN tunnel?

Can you access the printer config page (I assume this is a web page?) after you assign it a static IP (even if you can't print)?

The remote clients connect mostly using thin clients, through terminal services.

The config page is not accessible using the address that is assigned on the printer..64.xxx.xx.xxx

If I reset the IP on the printer to pick up the IP from the router and it is given a local IP, I can then access the config page.

You are going to have to nat a public address to you local private address then create your access list. Otherwise the users will have to come across a vpn, t1, etc...

Can you provide me with some documentation of how to do this?

Looking in my routers config page it looks like I will be able to do this.  Once I assign a WAN address to the local address, do I then point the printers driver, which is located on the terminal server, to the NAT address?

Terminal services?  

Where is the label printer?  Is it attached to the offsite client's network or the onsite network the terminal servers are on?  If the printer is on the offsite client's network are you using printer redirection?  

The printer is at the offsite.  It is attached to the offsite network.  Printer Redirection is enabled.

What port type does the printer use on the offsite client?  (LTP/USB/IP/etc...)

As of now it is using a USB to a local machine (at the offsite location).  From that you can use it, through printer redirection, while in a terminal session to the main site.  This alternative is to slow and takes at least 7 seconds for the printer to print.  Too time consuming!  What are some alternatives?

Anybody??

Are you using a ZebraNet card in this printer or do you have it connected to a JetDirect or some other type of print server? When it's not connected to a PC, that is...

Assuming it can be directly on the network, of course.

It is a JetDirect Print Server.  It can connect directly to the network.  Looking at it over the weekend I feel that it is in the Network settings of the router or the Print Server itself.  The Print Server will accept a local address from the offsite location, but then I will have to assign it a public address in order to print to it from a RDP session.  As of now the Printer is using Virtual Server to get to the local, but I have no way for the printer to understand that it needs to have a public address..64.xxx.....for example.  I have never set a printer up over a WAN before so this is rather difficult for me.  I appreciat all the help so far. I am hoping to get this issue solved soon.  Thanks.

If you've got a WAN you don't need to give it a public address.  It should be handled by the same routing functions that allow client/server connectivity across the WAN.

ShineOn:

Could you give me a possible setup scenario for this printer?  Here is how I can explain it.  The label printer is connected to a remote sites network where I have assigned it a static IP address with my D-Link router.  The remote site RDP's back to the main site and uses a softeware program that requires them to print labels.  So a thin client (remote site) that is in a RDP session( to the main site) will have to print to that label printer(remote site)??

I am still new to networking and learning as I go, so this is a little difficult and I seem to be struggling with it.  Thank you for all the help so far.  

RDP as in Windows Terminal Server or as in Windows Remote Desktop to someone's PC?

No actual WAN, just thin-client access over the 'net?  or is there a WAN link over which you can PING the print server?

Did you assign it a static IP address on the remote network or on your network?

Can you PING any other devices on the remote network?

If you can PING the printer from your site, you should be able to print to the printer from your site, unless you're blocking whatever protocol / port(s) you've set up the JetDirect to use.  
What did you set it up to use, by the way - LPR/LPD, JetDirect (port 9100) or something else?

At any rate, if you can print to it from your site, then you should be able to set it up on your TS as a printer, and give permissions to it to the remote clients.  I don't know exactly how in a pure TS environment - I'm a Citrix kind of guy - so maybe if you let us know what version/SP of TS you've got, we can cross-post in the appropriate zone to attract more TS-knowledgeable Experts.

RDP as in Windows Terminal Server, yes.  A thin client access over the net, yes.

I assigned it a static IP address on the remote network.

I can ping other printers on the remote network from my network...ping 96.xxx.xx.xx

I can not ping this printer.  It is set up to use port 9100 (JetDirect).

By assigning it a static IP on the remote network I can direct specific ports to that printer..port 9100...correct?  The static IP is local to the remote site...Remote site printer's IP on remote sites network--->192.xxx.xx.xxx??

Sorry for the confusion earlier, but thanks for sticking with me to try and help.  I appreciate it very much.  

Hi all
i can see that this conversation is not going nowhere. sorry if i am being harsh.
Dear Cbarbre. lets do it this way.
we first name the sites so every one knows what is where.
Site A (this is the site where you have the zebra printer)
forget about the other sites, first we have to make sure that your printer is fully functional on in your Site A.
so do the following

assign your Zebra printer (can you tell me what printer is it?) a static IP (from the Range that you are using in the Site A) subnet mask and default getaway. and make sure that no other device can get that IP in your Site A (or by reserving it in DHCP if you have it in Site A or just put it on paper and remember.)

for sure you have a PC in Site A which is connected to network and has the IP, subnet mask, default getaway of Site A.
so now when you are finished with all this send us the following.
IP config of the printer
IP config of the PC
and the type of the Zebra Printer.

don't wary this will wark.
relax:)

"By assigning it a static IP on the remote network I can direct specific ports to that printer..port 9100...correct?  The static IP is local to the remote site...Remote site printer's IP on remote sites network--->192.xxx.xx.xxx??"

"I can ping other printers on the remote network from my network...ping 96.xxx.xx.xx"

But... if the remote site's network is a 192 class A network, and the other printers on the remote network are 96 (class A?) then what's wrong with this picture?

Are the other printers on the remote network assigned public IP addresses, or did you miskey something?

If you have a WAN connection (even a site-to-site VPN connection) you should be able to PING all devices on the remote network, provided they have the correct subnet and default route (aka gateway).  

If you can access the JetDirect's embedded web server, you should be able to PING the server and create a printer object using TCP/IP printing and print to it from your site.

However, JetDirect print traffic across a slow link isn't necessarily the best way to do it.  You probably should do RDP printing.  You should be able to install the Zebra printer on the client PC's and use RDP redirection to the client PC's printer.  That should be less bandwidth-intensive than direct JetDirect printing across the WAN.

You could consider using IPP, too, which should be better bandwidth-wise than JetDirect protocol.  Depending, of course on whether or not your JetDirect can do IPP.  Even if you don't do it across the Internet directly, but, rather, across the WAN, IPP would be more efficient, IMHO, than JetDirect protocol.

artoaperjan:

The printer is a Zebra LP 2844 Label Printer.

I have attached the Printer's IP config and the Computer's config (location A).

Thanks for the help.  I hope I can get this problem solved, it is very frustrating...

Thanks for all the upcoming help in advance!!

                    Zebra LP 2844 IP config
  Serial Number:           2487364
  Ethernet Address:        xxxxxxxxxxx       Cable Type:        10BASET
  Speed:                   10Mbps             Link Status:       Good
  F/W Version:             7.02 (3111A)       Polarity:          Normal
 
  Rx Packets:              1643908            Tx Packets:        170859
  Rx Packets Unavailable:  0                  Tx Packet Errors:  0
  Rx Packet Errors:        0                  Tx Packet Retries: 0
  Checksum Errors:         0
 
Error:
  NetWare:                 None
  TCP/IP:                  Error reading from Telnet
 
 
NetWare (ENABLED)
  Mode:                    Unknown
 
  Print Server Name:       ZBR2487364
 
  SAP Interval:            1 Minute
  Frame Format:            Ethernet II
  Trap Destination:        00.00.00.00 : 00.00.00.00.00.00
 
 
TCP/IP (ENABLED)
  System Name:             ZBR2487364
  Web Address:             http://192.168.0.245
  IP Address:              192.168.0.245
  Subnet Mask:             255.255.255.0
  Default Gateway:         192.168.0.1
  Timeout Checking:        Enabled
  Trap Destination(s):     255.255.255.255
 
 
JetAdmin (ENABLED)
Port Configuration
  Name:                                       
  Printer Status:                             Online
  Language Switching:                         Off
  Bidirectional Communication:                Enabled
  Connected To:                               printer  - 
  Printer Panel Display:                      
  Error: None
 
 
 
 
Location (A)  Computer IP Config
 
IP Address:  			192.168.0.245
Subnet Mask:			255.255.255.0
Default Gateway:		         192.168.0.1
 
Preferred DNS Server:	         68.230.0.12
Alternate DNS Server		68.230.112.12

Select allOpen in new window

The printer IP address and the computer IP address is the same.

The printer should have its own IP address.

Sorry, that is a typo on my part.  Here is the correct informationfor the PC.  The printer address is correct.

     Location (A)  Computer IP Config
 
IP Address:  			192.168.0.251
Subnet Mask:			255.255.255.0
Default Gateway:		         192.168.0.1
 
Preferred DNS Server:	         68.230.0.12
Alternate DNS Server      		68.230.112.12

Select allOpen in new window

Hi cbarbre

First Does your LP 2844 has a built in network card ?
i don't think. we have some of them and they don't but any how i need to make sure.

so as i undersand from your configs you have sent you have connected your printer to a network print server, is this correct ?
if yes then where is the IP configuration? by IP configuration i need only the
IP address:
Subnet mask:
Deafult getway:

above you have clearly mantioned the Computer configuration but above that as ShineOn mantioed you have two similar IPs. so we need to sort this out before going forwad.
so pleas once more can you fill in the following and send to us

Network Print server:
IP:
Mask:
Gateway:

Computer in network A:
IP:
Mask:
Gateway:

also pleas tell us how have you connected your LP 2844 to your network printer?
USB, LPT, SERIAL, COM... and to what port? on the network print server.

so getting this info will be just a second.
something else to try.

1. from your computer in netork A ping your network print server that you have connected our LP 2844 which is in network A. let us know the result.

2. open your netork print servers web page and print a test page or the configuration on your LP 2844.
let us know if you have succided.

3. on PC in network A setup a printer network port.
 a. open printers folder
 b. right click on an open area
 c. choose server propertiec
 d. go to Ports tab
 e. click on add port...
 follow the wizard
 when type in your network print servers IP to which the LP2844 is connected.
 and then on some step it will ask which port you want to choos so choose the one to which you have connected your LP2844, like LPT1 USB1 COM1 ..... it is doesn't ask just contenue and finish.

4. Install the printer drivers of LP 2844 on your PC in network A and add a Local printer but choose your IP port you have created.
and after that try to print a Test Page from your PC you should be able to see something comming our some texts.

so this is for now don't worry we will solve your problem just have some patience

so let as know what happend on all the 4 steps i have asked you to do.

ok Talk to U.

artoaperjan,

cbarbre already said the Zebra is attached to an external JetDirect print server.  I already asked if it had a Zebranet card or if it was connected to a JetDirect...

The printer does have a built in Card.  Would you suggest that I use that?  If that is easier to set up than I am game....( My biggest problem is the networking..I still have a lot to learn) This problem is seeming to get worse every day.....

Thanks.

ShineOn:

Thank you for the information.  I have the printer on Network A's LAN.  I can ping it.  I can install on all other "Fat Client computers" by setting it up via local port, and use RDP redirection to print to it while in a terminal services session.  How doI print to it on the "thin clients"?  

1. Add printer to terminal server( Add printer/ Local Printer attached to this computer/ Hp Standard TCP/IP Port/ "Supply IP Address"/"Supply Additional Information as: Custom, Raw, Port 9100./Finish)

2.  Now after this setup, I will try to print to printer but the job stays in the que, then times out.

3.  Can I assign it a static local IP from router, and a static public IP in Printers network settings?

Please ask all questions you have... I know that I am making this way more difficult than it really is!!

I am confused as to what you mean by "thin client" vs "fat client." If it's via RDP, it's "thin client" by definition.

Do you mean you have some "thin client" devices along the lines of Winterms, that wouldn't be able to do the RDP redirection?

If you can actually print to the printer from the server across the WAN, perhaps you could consider changing the technology from HP port 9100 to use LPR/LPD, or even better, IPP.   HP protocol is more resource-intensive and bidirectional-response dependent and is probably timing out.

artoaperjan:

Yes.  I can ping and print from computers in network A to the Zebra printer in network A.
In network A I have a D-Link 604LB router that is also connected to the internet.
In network B I have an Edimax ER-1088 router that is also connected to the internet.
These routers both have advanced features.
I can ping router in Network A from my pc in Network B.  I can ping router in Network B from computer in Network A.
I am ready for further instructions.

ShineOn:

By "thin client" I do mean that we use Winterms.  By "fat client" I simply meant that it was a Computer using RDP.  Most of our users use WYSE Winterms.  They are the ones whom will need to print to the printer.

ok ok now this is becoming really OK :)

so just a question.
did you try to print on our Zibra printer (in network A) from a PC (in network B)
if it is YES then you are done with %90

now the real question is.
above you are talking about thin client and RDP and what ever.
can you exactly describe following

What are your users using ? (PC or Thin client)
to what network system are they connected to? (PC network Domain or Thin client Terminal/Citirx)
from which network you want your users to print on Zebra (in network A)
What application they are going to print from?
and any other info you think might be useful to us. pleas remember to always write network A or B so we have clear understanding what you are going to talk about.

ok fried we are nearly there.

I can print from computer (in network A) to Zebra printer in (network A).  I can not print to printer (in network A) from computer (in network B).

Users are using thin client (WYSE Winterms).
Users connect to (network B) terminal server.  Users using WYSE Thin Clients (in network A) connect to terminal server (in network B).  Users using WYSE Thin Clients (in network B) connected to terminal server in (network B) should be able to print to Zebra printer (in network A).
The application they are printing from is named Centricity.

If this next comment is confusing then ignore..I am just hinking here...  I have another Zebra Label printer in (network C).  Users (in network C) use WYSE Thin CLients to connect to terminal server in (Network B).  I in (network B), can print to Zebra Printer in (Network C), as if it was a local printer.  It sets on a public static IP assigned to us by the ISP.  Thoughts??