Discussion Locked

IPP Printing

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi everyone,

I can't seem to get IPP Printing to work over the internet. I have 2 printers shared on my proxy which is running Win2k and ISA server, and I have all of the ports open for testing. When I try to put in the address to even view the printers shared (http://ipaddress/printers) it comes up with

An error occurred processing your request.

Error Code: 80070035
Note: Get ADSI Printers

I looked on the Knowledgebase, and they say to enable File and Printer sharing on the external adapter of the proxy, and then use it to shut down ports not being used. I tried this and still no go. Also, when I try and add a printer on my computer to print to that shared printer, (http://ipaddress/printers/sharename) it comes up with Youmust type in a username and password to use this printer. So I type in one that is valid on that network, and then it says

Could not connect to the printer. You either entered a printer name that was incorrect or the specified printer is no longer connected to the server.

I know that the printer share name is correct, and that it is connected to the server. I can print locally on that network by adding the shared printer, but when i try to print remotely it's no go. Any ideas?

6 replies

by estebandelatorre

DNS is the most important thing to check. If the printer name can't be resolved by dns, windows 2000 won't print.
All internet printing will rely on DNS name solving!!!
Step 1:
Ping by ip_address in order to check good conectivity.
Step 2: Add an "A" record in order to reach the printer on the other side and ping it using it's name.
(also confirm that the host that is responding IS your printer - by removing it's cable for a few pings)
Once the printer can be reached by it's fully qualifyname (like printer1.lan-A.com)
you can start the printer definition in your lan, refering the printer by it's fully name.

Good Luck!

by -=otverge=-

Unfortunately, the printer is behind an ISA server, and therefore has a private IP. I don't believe this solution will work, we already have connectivity to the ISA server.

by rvkempen

Actually, mister edt is partially right.
If you want to connect to a printer with a private ip address, you really want this one translated to a public one.
If you have ip adresses free, make a nat translation from your free public address to the printers private ip address.
Now if this is done you've got the dns problem to resolve.
If your internal dns server is accesible from the outside, change your local ws dns to this one.
If you have your own dns "internet" server, make sure the printer is known in the dns server.
This is a way of letting it all work, but you make a big security risk.
Why not make a vpn connection to your w2000 network, and don't compromise your security.
This way you can logon to your domain, with all the file/printer options you have while working "at the office".

Greets Ron.

by -=otverge=-

Ok, this is not a network printer. It is phyically connected to another PC on the internal network, and it is being shared on the proxy. I can't make any DNS entries, or do and NAT because I only have 1 IP address which is being used by the proxy.
I've had this working before, but it was with Win NT. I don't understand why it will not work now with 2000. Anyone else?

This discussion is closed to new replies.