W
Wayne Erfling
I have a computer I own with a parallel printer directly attached (HP
OfficeJet R40).
Connected to the same DSL router (one box) is my tele-commuter,
company-owned computer on a (remote, VPN) domain.
I don't have any trouble sharing my personal folders with my company
computer, and I can see my shared printer from the company computer, but
when I try to connect to the printer (either via Add Printer or "Open" from
the share box) it takes 2-5 minutes, after which the printer is added to my
company computer but when I try to use it it doesn't work.
There are no security errors logged in the Event Viewer of my personal
computer.
While I am an IT professional I am not a network techie, so I can't tell
what's happening if there's no trail of bread crumbs in Event Viewer.
Of course I can execute NET or NETSTAT commands with assistance, etc.
It's really inconvenient to not be able to use my (personal) printers from
my company computer. By the way, it worked at one point but now the
behavior described above is consistent through many reboots and trials.
I've already scoured Microsoft and the net and couldn't find this problem.
Any help appreciated.
OfficeJet R40).
Connected to the same DSL router (one box) is my tele-commuter,
company-owned computer on a (remote, VPN) domain.
I don't have any trouble sharing my personal folders with my company
computer, and I can see my shared printer from the company computer, but
when I try to connect to the printer (either via Add Printer or "Open" from
the share box) it takes 2-5 minutes, after which the printer is added to my
company computer but when I try to use it it doesn't work.
There are no security errors logged in the Event Viewer of my personal
computer.
While I am an IT professional I am not a network techie, so I can't tell
what's happening if there's no trail of bread crumbs in Event Viewer.
Of course I can execute NET or NETSTAT commands with assistance, etc.
It's really inconvenient to not be able to use my (personal) printers from
my company computer. By the way, it worked at one point but now the
behavior described above is consistent through many reboots and trials.
I've already scoured Microsoft and the net and couldn't find this problem.
Any help appreciated.