|
|
| Author |
Message |
rullman
Joined: 12 Oct 2006
Posts: 1
|
 Posted: 10/12/06 - 04:00 Post subject: Cannot set up network printer |
 |
|
Hello. I'm having difficulties setting up my HP printer for sharing on a Win Server 2003 LAN. The situation is this: Desktop computer, w/HP computer and DSL modem connected to it directly. Two laptop computers, connected to the desktop via a Linksys router. Both laptop can share the internet connection, but only one can share the printer; the other one, when I attempt to connect, gets "Windows cannot connect to the printer. Either the printer name was typed incorrectly (it wasn't!), or the specified printer has lost its connection to the server (it hasn't!)." Can anyone guide me through troubleshooting here? Thanks in advance.
|
|
|
Back to top
|
|
|
|
 |
ridlon
Joined: 12 Oct 2006
Posts: 1
|
| Posted: 04/16/07 - 11:13 Post subject: |
|
|
I'm not exactly a Windows networking expert, but I'll try to tackle to obvious ones before someone with more experience comes along. First, from the laptop, type \\ to see a list of shared resources; if the printer shows, right-click and try to connect; if it doesn't, tell us. Second, what firewalls do you have running on the three machines, and Have you tried disabling them to see if printer sharing works that way?
|
|
|
Back to top
|
|
|
|
|
mruxsaksriskul
Joined: 28 Feb 2008
Posts: 1
|
| Posted: 02/28/08 - 19:49 Post subject: |
|
|
Trigger: When attempt to add a printer the directory you receive the below message.
Error: Windows cannot connect to the printer. Either the printer name was typed incorrectly, or the specified printer has lost its connection to the server.
Hey,
Hope this makes sense. We were having the same issue and the resolution I found was to create a subnet under Active Directory Sites and Services matching our topology then I associated with our site. Ours was simple enough we only have one subnet for our entire network. This changes can be made live it didn’t affect anything from what I could tell. It did take a while for the info to replicate before the clients could transcend the AD topology.
You can find a helpful link here at expert’s exchange
http://www.experts-exchange.com/Hardware/Peripherals/Printers_Scanners/Q_22603791.html#a19207617
The other thing I did was to edit the local policy on our one printer server it hosts about (20printers). The change made was enabling the “Check published state” and setting it to check at 1hr intervals. You can get to the local policy by:
Go to run type “gpedit.msc”
Under Computer Configuration expand Administrative Templates
Then explain Printers and enable the policy “Check published state”.
The problem I think we had is our printers are on the 192.168.0 subnet and the workstations are on 192.168.1 I’m not sure when it broke but this fixed it for us. I believe client machines use the AD sites and subnets to navigate to the printer via the right subnet. Which is outside of DNS which is why we could add the printer any other way i.e. \\servername\printer or \\xxx.xxx.xxx.xxx\printer out side of AD.
Hope this helps!
Thanks,
Michael
“Freely you have received, freely give.” |
|
|
Back to top
|
|
|
|
|
|
