Printing to a TCP/IP port which is on a different IP range. Can ping printer but get error when printing
Hello,
I have a problem printing to a TCP/IP port which is at a remote location. The locations are setup with a permanent VPN. In the past I have printed to this printer in the same way as I am trying to now. The only difference is that I have a new Windows 2003 server which is the computer from which I wish to print to the printer. In the past the computer which used the remote printer was a SBS 2000 server.
I can ping the printer and it says ready as if its right to go. But it returns an error every time I print.
The IP range on the server network is 192.168.15.xxx (Server 2003 = 192.168.15.11)
The IP range in the remote network is 172.16.20.xxx (Printer = 172.16.20.99)
Is there any reason that this would not work on Windows 2003 when it did on Windows 2000 SBS. Note: When I first set it up on 2000 SBS it went first go, No issues)
I have tried a PCL and Postscript driver for the printer.
Does anyone have any suggestions for me? All advice appreciated.
Thanks,
Mark
I have a problem printing to a TCP/IP port which is at a remote location. The locations are setup with a permanent VPN. In the past I have printed to this printer in the same way as I am trying to now. The only difference is that I have a new Windows 2003 server which is the computer from which I wish to print to the printer. In the past the computer which used the remote printer was a SBS 2000 server.
I can ping the printer and it says ready as if its right to go. But it returns an error every time I print.
The IP range on the server network is 192.168.15.xxx (Server 2003 = 192.168.15.11)
The IP range in the remote network is 172.16.20.xxx (Printer = 172.16.20.99)
Is there any reason that this would not work on Windows 2003 when it did on Windows 2000 SBS. Note: When I first set it up on 2000 SBS it went first go, No issues)
I have tried a PCL and Postscript driver for the printer.
Does anyone have any suggestions for me? All advice appreciated.
Thanks,
Mark
ASKER
OK Thanks Steve.
I tried LPQ -S ipaddress -P lp and it said "no entries" I check the configuration and it is set to LPR Port 515.
I couldnt telnet to port 9100.
I can telnet to port 515
When i looked up the event viewer I see this
Event Type: Error
Event Source: Print
Event Category: None
Event ID: 6161
Date: 27/04/2006
Time: 2:58:02 PM
User: RSM\trim
Computer: RSM-SERVER2003
Description:
The document Test Page owned by trim failed to print on printer Canon GP215 PCL 5e. Data type: NT EMF 1.008. Size of the spool file in bytes: 196608. Number of bytes printed: 0. Total number of pages in the document: 1. Number of pages printed: 0. Client machine: \\RSM-SERVER2003. Win32 error code returned by the print processor: 2250. This network connection does not exist.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
I searched the error code 2250 and it says that I should troubleshoot connectivity but Im stumped since i can ping the machine and telnet to it and the LPQ responds
I tried LPQ -S ipaddress -P lp and it said "no entries" I check the configuration and it is set to LPR Port 515.
I couldnt telnet to port 9100.
I can telnet to port 515
When i looked up the event viewer I see this
Event Type: Error
Event Source: Print
Event Category: None
Event ID: 6161
Date: 27/04/2006
Time: 2:58:02 PM
User: RSM\trim
Computer: RSM-SERVER2003
Description:
The document Test Page owned by trim failed to print on printer Canon GP215 PCL 5e. Data type: NT EMF 1.008. Size of the spool file in bytes: 196608. Number of bytes printed: 0. Total number of pages in the document: 1. Number of pages printed: 0. Client machine: \\RSM-SERVER2003. Win32 error code returned by the print processor: 2250. This network connection does not exist.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
I searched the error code 2250 and it says that I should troubleshoot connectivity but Im stumped since i can ping the machine and telnet to it and the LPQ responds
OK, so LPR is working. Try creating a new TCP/IP port for the printer using the ipaddress rather than name and lp as the queue name to see if that helps.
You can send a quick test text file to the printer using command line too if you wish,
LPR -S ipaddress -P lp sometextfile.txt
Steve
You can send a quick test text file to the printer using command line too if you wish,
LPR -S ipaddress -P lp sometextfile.txt
Steve
ASKER
Steve,
After creating a text file called test.txt. I did
LPR -S ipaddress -P lp test.txt
and got "Error: Print Server did not accept request. Job aborted."
As far as creating a TCP/IP port using the IP address rather than the name. Im not sure. I think that is how I did do it in the first place.
When i created the port I did input the IP address 172.16.20.99 and the name of the port showed as IP_172.16.20.99
Mark
After creating a text file called test.txt. I did
LPR -S ipaddress -P lp test.txt
and got "Error: Print Server did not accept request. Job aborted."
As far as creating a TCP/IP port using the IP address rather than the name. Im not sure. I think that is how I did do it in the first place.
When i created the port I did input the IP address 172.16.20.99 and the name of the port showed as IP_172.16.20.99
Mark
ASKER
BTW Steve,
The printer does print at the remote location form local workstations. So I know it is working.
I used the same driver as they use also.
Mark
The printer does print at the remote location form local workstations. So I know it is working.
I used the same driver as they use also.
Mark
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
i tried raw. it didnt work. Im not sure about lpt1. I dont know how you set that up.
As for the printer queue name i will have to investigate further. But you could be onto something. I now have a vague recollection of a different queue name.
I have the old server. I just got it back 10 minutes ago. But the HDD has a problem and it wont boot up. Or at least it hasnt been.
They have sent it back to me to be looked at which I am about to do.
Thanks MARK
As for the printer queue name i will have to investigate further. But you could be onto something. I now have a vague recollection of a different queue name.
I have the old server. I just got it back 10 minutes ago. But the HDD has a problem and it wont boot up. Or at least it hasnt been.
They have sent it back to me to be looked at which I am about to do.
Thanks MARK
OK, This table:
http://www.digitalissues.co.uk/html/hardware/charts/names.html
suggests print q might have to be 'print' or possible print_215. Case may or not be important here so try a new tcp/ip port with ip address and print as the queue name -- or you can try with the LPR command above before configuring Windows if you want.
Steve
http://www.digitalissues.co.uk/html/hardware/charts/names.html
suggests print q might have to be 'print' or possible print_215. Case may or not be important here so try a new tcp/ip port with ip address and print as the queue name -- or you can try with the LPR command above before configuring Windows if you want.
Steve
ASKER
i put in the queue name print_200-216. Found on http://www.digitalissues.co.uk/html/hardware/charts/names.html.
I just found it myself also. LOL
Well. It doesnt give an error when I print a test page. It goes somewhere but not to printer
Mark
I just found it myself also. LOL
Well. It doesnt give an error when I print a test page. It goes somewhere but not to printer
Mark
Oh. Second silly question then. How are the local users who can print connecting to the printer. Could you not get one of them to check the port used...
Steve
Steve
Also did you try just 'print', or maybe print_215 which is what I think it means (i.e. use the model no.)
ASKER
Steve,
Tried a few combos and still seeing print jobs go somewhere but not to printer.
You suggest LPR command but what would be the syntax of that if I want to specify the queue name?
Mark
Tried a few combos and still seeing print jobs go somewhere but not to printer.
You suggest LPR command but what would be the syntax of that if I want to specify the queue name?
Mark
That is using LPR. I meaned to do a test using the command line like above:
LPR -S ipaddress -P print test.txt
etc.
if you do
LPQ -S ipaddress -P print
then it will tell you if it thinks there is anything in the Q now.
It might be worth re-starting hte Print Spooler service on the server now and/or reset the printer just in case anything is stuck in it's buffers etc.
Can you find out what the working users are set to?
LPR -S ipaddress -P print test.txt
etc.
if you do
LPQ -S ipaddress -P print
then it will tell you if it thinks there is anything in the Q now.
It might be worth re-starting hte Print Spooler service on the server now and/or reset the printer just in case anything is stuck in it's buffers etc.
Can you find out what the working users are set to?
ASKER
Steve,
Breathe easy my good helper. I walked away for a bit and came up with checking the remote location too. Man, its always something silly that you overlook hey.
Thats why we need another fresh set of eyes i guess.
Checked out remote pc and found that I had to tick LPR bye counting enabled. Voila. print straight away.
Great work mate. Thanks heaps for your help
Best Regards
Mark
Breathe easy my good helper. I walked away for a bit and came up with checking the remote location too. Man, its always something silly that you overlook hey.
Thats why we need another fresh set of eyes i guess.
Checked out remote pc and found that I had to tick LPR bye counting enabled. Voila. print straight away.
Great work mate. Thanks heaps for your help
Best Regards
Mark
Ah well, wasn't any of my suggestions but there you go :-) Different print servers can be a PITA to get working, especially old ones on new OS's... Ok they all use the same 'standard' but since when were standard's standard.
Anyway enough ranting, glad if it helped point you the right way.
Steve
Anyway enough ranting, glad if it helped point you the right way.
Steve
BTW I see this is theoretically your first Q so you'll find an Accept button next to one of the comments when you are done :-)
ASKER
Steve,
Your help was unreal. It certainly got me facing in the right direction.
This is the first question I have put up on here and I am impressed.
I assume that I just accept one of your answers to close question and give you the points.
Is that right??
Mark
PS Thanks again
Your help was unreal. It certainly got me facing in the right direction.
This is the first question I have put up on here and I am impressed.
I assume that I just accept one of your answers to close question and give you the points.
Is that right??
Mark
PS Thanks again
ASKER
Ahh we think alike again
Yup.
it should respond "nothing in q" or similar if it is accessible over LPR. Maybe when you setup the port for the printer on the server you (or it decided) set it up to use port 9100 printing rather than LPR (port 515) or the other way around and potentially you have a firewall rule for only one of the two on the VPN link?
To see if you can talk to port 9100 try
and/or
telnet ipaddress 9100
Press Return. If it brings up a blank screen you can connect, if it errors or times out then you can't.
Press Control [ to exit then type quit.
Steve