Network printer communication

[salkin]

I have installed WinGate on my home network consisting of 6 PCs and a network printer. The printer is a laser printer with a built in network interface and it has a special IP address in the network.
All the PCs reach the Internet via the WinGate server in a perfect way, but they cannot get in contact with the printer. It seems like the print requests are taken over by WinGate who tries to do something with them that I do not understand, and after about 20 to 30 seconds the PC print driver reports that the printing failed.

Is there anyone who has run into this problem and has some hints to share?

Lars N

[genie]

What happens if you stop Wingate? Can your network clients use the printer then?

[labull]

Do you see any entries in the Firewall tab of GateKeeper?

We've found printers often use Port 161 or 9100 to communicate.

[salkin]

What happens if you stop Wingate? Can your network clients use the printer then?

That doesn't seem to help. I have stopped both the WinGate server and the client without effect.

[genie]

How are your client connected out? Do they use WGIC or plain NAT?

[salkin]

I connect via WGIC.
I made the installation in the way that seemd most simple to me, so when the installation program aked to install the WGIC I answerd yes. The installation completed and I started t access the Internet. A few days later when I wanted to print a document I discovered the printer problem.

[labull]

I recommend uninstalling WGIC and using NAT - just set the Default Dateway on each system to the IP address of the WinGate server.

This should allow printing and Internet access.

Larrry

[genie]

Either that or - alternatevely - set the WGIC access for the print spooler to all local.

[bhollna92000]

You just need to uninstall the client. We have/had the same problem. But the idea about the firewall interfering with the port 9100 is a interesting idea. I will have to check on that and other port options because we would really like to use WGIC.

Brian