Error 0x00000709 when connecting to network printer

  • Thread starter Thread starter Sandy Wood
  • Start date Start date
S

Sandy Wood

I've setup a Dell 5100cn printer on a Windows 2008 x64 server for our Vista
users to print on. I added a x86 driver for our x86 Vista users. I'm running
Vista x86 and I can connect to the printer without problem. We've got 3 x64
Vista systems that cannot connect to the same printer, they recieve an error
0x00000709 when they attempt to connect. I've checked the permissions and
they all appear to be set correctly - Everyone can print. Any idea what might
be missing to allow them to print?
 
E:\>winerror 0x00000709
1801 ERROR_INVALID_PRINTER_NAME <--> No NTSTATUS matched

I'm stumped since the x86 machines connect okay

Try installing the driver on the client machine, then make the connection.
If that works I'm still stumped.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Well at least I've got the 'printer name invalid' to check on. Thanks for the
try, I'll see what I can find. By the way, there's no order that the drivers
(x86, x64) appear to a client when they attempt to connect is there?
--
Sandy Wood
Orange County District Attorney


Alan Morris said:
E:\>winerror 0x00000709
1801 ERROR_INVALID_PRINTER_NAME <--> No NTSTATUS matched

I'm stumped since the x86 machines connect okay

Try installing the driver on the client machine, then make the connection.
If that works I'm still stumped.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.
 
the client's going to pull the driver provided by name, then architecture
(x86, x64).

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.

Sandy Wood said:
Well at least I've got the 'printer name invalid' to check on. Thanks for
the
try, I'll see what I can find. By the way, there's no order that the
drivers
(x86, x64) appear to a client when they attempt to connect is there?
 
Back
Top