Can't print to TCP printer


F

Fokke Nauta

Hi all,

We have a new laptop with Win 7 64 bits. It is wireless attachted to our
LAN. In the LAN we have a printserver running on XP Pro 32 with a printer
attached. We have not been able to install a network printer on the laptop
simply because there is no Win 7 driver for that printer. So on the
printserver I created a TCP/IP queue for that printer. The queue works, as I
was able to print by LPR on a remote Ubuntu machine. I have created a TCP
printer on the Win 7 laptop and was - to my surprise - able to install a
printer driver. On the server I could see that the laptop contacts the
server on port 515 when I want to print. Of course the firewall is open for
that port. Nothing happens and no printout appears. The printer does not
even initialize. On the laptop an exlamation mark appears on the printer
symbol with a "printer error" announcement, and the job remains in the local
queue.
On the laptop there is a sort of "problem solving" and after I have started
that, it wants to share the TCP printer with the home group (which I don't
have).
The LAN works OK; all PC's, the printserver and the laptop can see eachother
and are able to share files and directories.

Anyone got an idea as how to get the laptop to use the printer?

Many thanks in advance for your help.
With kind regards,
Fokke Nauta
 
Ad

Advertisements

G

Gene E. Bloch

Parko's reply was a bad pun, even for a native speaker of English :)

It is possible, but not certain, that a driver for Windows Vista would work
on your laptop. Check on the printer manufacturer's site...
 
Ad

Advertisements

D

Dave

Fokke Nauta said:
Hi all,

We have a new laptop with Win 7 64 bits. It is wireless attachted to our
LAN. In the LAN we have a printserver running on XP Pro 32 with a printer
attached. We have not been able to install a network printer on the laptop
simply because there is no Win 7 driver for that printer. So on the
printserver I created a TCP/IP queue for that printer. The queue works, as
I was able to print by LPR on a remote Ubuntu machine. I have created a
TCP printer on the Win 7 laptop and was - to my surprise - able to install
a printer driver. On the server I could see that the laptop contacts the
server on port 515 when I want to print. Of course the firewall is open
for that port. Nothing happens and no printout appears. The printer does
not even initialize. On the laptop an exlamation mark appears on the
printer symbol with a "printer error" announcement, and the job remains in
the local queue.
On the laptop there is a sort of "problem solving" and after I have
started that, it wants to share the TCP printer with the home group (which
I don't have).
The LAN works OK; all PC's, the printserver and the laptop can see
eachother and are able to share files and directories.

Anyone got an idea as how to get the laptop to use the printer?

Many thanks in advance for your help.
With kind regards,
Fokke Nauta
You said the ports are open in the firewall, are UDP and TCP both open? If
not, you will only get communications one way.
Just a thought,
Dave
 
P

Parko

Parko's reply was a bad pun, even for a native speaker of English :)

It is possible, but not certain, that a driver for Windows Vista would
work on your laptop. Check on the printer manufacturer's site...
I resemble the rite to macerate the Queen's English just like any other
red knackered maroon.
 
F

Fokke Nauta

Dave said:
You said the ports are open in the firewall, are UDP and TCP both open? If
not, you will only get communications one way.
Just a thought,
Dave
Hi Dave,
Yep, the firewall on the server is open wide for all local adresses in the
LAN, including the laptops. All ports and protocols.

Fokke
 
F

Fokke Nauta

Gene E. Bloch said:
Parko's reply was a bad pun, even for a native speaker of English :)

It is possible, but not certain, that a driver for Windows Vista would
work
on your laptop. Check on the printer manufacturer's site...
You are right, in many occasions this would work. I already searched for a
Vista driver for my printer. None available.
I guess the printer (HP3650) is already too old.

Fokke
 
G

Gene E. Bloch

I resemble the rite to macerate the Queen's English just like any other
red knackered maroon.
But you can't without my permission. Or can you? I forget...

Bad puns are OK, as we all know, but it can be a tad unfair dropping them
on a non-native speaker.
 
Ad

Advertisements

G

Gene E. Bloch

You are right, in many occasions this would work. I already searched for a
Vista driver for my printer. None available.
I guess the printer (HP3650) is already too old.

Fokke
Sounds like. BTW - I like the word "superannuated" - it applies to me as
well as to your printer :)
 
D

Dave

Fokke Nauta said:
Hi Dave,
Yep, the firewall on the server is open wide for all local adresses in the
LAN, including the laptops. All ports and protocols.

Fokke
I'm not sure why, but I was having trouble with an HP printer communicating
through the router firewall even though the computer could see the printer
and had it's IP and MAC addresses. Router tech support told me to manually
add access for ports 90 & 95, even though I had all ports open access for
the printer. Haven't had a chance to research it and it didn't work for me,
but maybe it will help you.
One other thought, I'm not sure why, but I hooked my printer up direct to
computer with ethernet cable, installed it on the computer and
communications were good. Shut printer off, removed it from the list of
printers in control panel, then hooked printer back up to router with
ethernet cable. Went back into software install and told it to add a device
and selected a wired ethernet connected printer, which it found and
installed and communications with printer were good. The only reason I can
think of is there was a file not being installed, that the printer needed
for communications, when I was trying to install it with it connected to
router, but when it was connected direct to computer the file got installed.
When I then connected printer to router the file was on the computer that it
needed. All speculation, but I'm super-anal and it has kept me from going
completely crazy. :-D
Might be worth a shot for you.
HTH,
Dave
 
F

Fokke Nauta

Bob I said:
OK, thanks.
I installed the printer locally on the laptop on the USB port, and the
driver installed perfectly. The printer works locally. So it is not
obsolete.
But when I connect the printer to the server and try to install a network
printer on the laptop, it finds the printer. It cannot find a driver and
wants an .INF file. The only .INF file I have is from the XP32 driver, which
won't work. I am not able to download the driver from the server (XP32).
When I install the printer on the laptop as a TCP/IP printer, I am able to
install the driver. So - this seems the way to go. When I try to print, it
contacts the server on port 515, but it does not print. The job sits in the
local queue.

Hence my question as how to solve this.

Fokke
 
F

Fokke Nauta

Gene E. Bloch said:
Sounds like. BTW - I like the word "superannuated" - it applies to me as
well as to your printer :)
To me as well :)
Can still remember the days of CP/M.

But the printer complies with W7. I can install a driver when I connect the
printer directly.

BTW, the laptop was in one piece :)

Fokke
 
Ad

Advertisements

F

Fokke Nauta

I'm not sure why, but I was having trouble with an HP printer
communicating through the router firewall even though the computer could
see the printer and had it's IP and MAC addresses. Router tech support
told me to manually add access for ports 90 & 95, even though I had all
ports open access for the printer. Haven't had a chance to research it and
it didn't work for me, but maybe it will help you.
One other thought, I'm not sure why, but I hooked my printer up direct to
computer with ethernet cable, installed it on the computer and
communications were good. Shut printer off, removed it from the list of
printers in control panel, then hooked printer back up to router with
ethernet cable. Went back into software install and told it to add a
device and selected a wired ethernet connected printer, which it found and
installed and communications with printer were good. The only reason I can
think of is there was a file not being installed, that the printer needed
for communications, when I was trying to install it with it connected to
router, but when it was connected direct to computer the file got
installed. When I then connected printer to router the file was on the
computer that it needed. All speculation, but I'm super-anal and it has
kept me from going completely crazy. :-D
Might be worth a shot for you.
HTH,
Dave
Strange things happen with printers ...
I connected the printer locally and the driver installed perfectly.
I hooked the printer to the server again, I could find the networked printer
on the laptop but wasn't able to install a driver. It insisted to find an
..INF file - which I only have from the XP32 driver on the server. It didn't
like that one.
So this did not work for me.
The only way to install the driver on the laptop is either locally or as a
TCP printer.
And that doesn't print.
Thanks anyway :)

Cheers,
Fokke
 
C

Char Jackson

I'm not sure why, but I was having trouble with an HP printer communicating
through the router firewall even though the computer could see the printer
and had it's IP and MAC addresses.
That's a pretty uncommon configuration (for home/SOHO anyway), to have
a router in between the computers and the printer. Much more often,
even if everything is physically connected to a "router", the devices
on the LAN side are only separated by a switch (I mean the switch
inside the router). Thus, router firewall and opening various ports
are completely unrelated and unnecessary to proper operation.
Router tech support told me to manually
add access for ports 90 & 95, even though I had all ports open access for
the printer. Haven't had a chance to research it and it didn't work for me,
but maybe it will help you.
I'm curious to know how things are physically connected. It's likely
that ports didn't need to be opened.
 
G

Gene E. Bloch

To me as well :)
Can still remember the days of CP/M.
I started in Fortran II and FAP on IBM 7090's in the early 60's. My phone
is much more powerful and has a far better user interface than those
machines, but it's much smaller :)

But now I have to learn Java and Android programming for the phone I want
to get next.
But the printer complies with W7. I can install a driver when I connect the
printer directly.

BTW, the laptop was in one piece :)
Oh, it must be a 1-bit computer.

....I would apologize for that remark, but I am by nature shameless :)
 
Ad

Advertisements

G

Gene E. Bloch

OK, thanks.
I installed the printer locally on the laptop on the USB port, and the
driver installed perfectly. The printer works locally. So it is not
obsolete.
But when I connect the printer to the server and try to install a network
printer on the laptop, it finds the printer. It cannot find a driver and
wants an .INF file. The only .INF file I have is from the XP32 driver, which
won't work. I am not able to download the driver from the server (XP32).
When I install the printer on the laptop as a TCP/IP printer, I am able to
install the driver. So - this seems the way to go. When I try to print, it
contacts the server on port 515, but it does not print. The job sits in the
local queue.

Hence my question as how to solve this.

Fokke
I am a little bit out of my depth here, but I'll take a chance and waste
your time with what I think.

As I understand it (and as I think I recall), installing the driver
directly (via USB, for example) on the problem computer (call that computer
"A") is a necessary first step to using the printer on the network.

The second step is to then connect the computer via the network instead of
directly to A (or just remove the USB connection from A, since the printer
is probably already on the network)

The third step is go to the printer's settings on A, go to the Ports tab,
and choose the network as the port for the computer.

This should now allow you to print from A.

I believe this is not new to you, but I am posting it just in case it is
different from what you have already tried.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top