Vista - Cannot connect to network printer, error 0x000006d1 (was OK with W

Just moved from the old trusted Windows 2000 T20 Thinkpad laptop to the new
Vista T61 laptop. I have a private wireless network, with a NAS (Buffalo
LinkStation) on it and a printer connected to the NAS via USB. I am trying to
connect to the printer but I keep receiving the error "0x000006d1".

Details: on my new laptop I can see the Buffalo LinkStation connected to my
network (though sometime I have to refresh the search a few times before it
gets correctly picked up) and I can navigate into the "Printers" folder in
it. But when I right-click on the printer icon and click "Connect..." I get
the error message "Windows cannot connect to the printer. Operation could not
be completed (error 0x000006d1)." Strangely enough a couple of times (out of
20+) this procedure worked instead and the printer was "successfully"
connected, but the first time it couldn't print (just nothing happened when I
clicked the Print b0tton) and the second time it was incredibly slow (i.e.
10min per page).

What I have already tried:
- disabled all firewalls
- installed the latest version of the printer driver
- installed the latest version of the Buffalo LinkStation firmware
- run a patch to allow Vista to work with the Buffalo LinkStation (available
on the Buffalo website)
- tried connecting to the Linkstation using the IP address insted of the name
- disabled IPv6 for this connection
- upgraded the router to a new, faster one (D-Link DIS-625, draft-n)
- as you can imagine re-booted all that can be re-booted

Nothing worked, and I'm out of ideas. And I'm seriously considering going
back to the old Win2K laptop! Thank you for your help!

E:\>winerror 0x000006d1
1745 RPC_S_PROCNUM_OUT_OF_RANGE <--> 0xc002002e
RPC_NT_PROCNUM_OUT_OF_RANGE

this means that the whatever is happening between the device and Vista over
the RPC (remote procedure call) transport is not supported.

It would better to create a local printer to the device rather than a
connection.

Does the print server device support TCP raw printing or the LPD service?
If it does create a Standard TCP/IP Port to the device. Follow the vendor
instructions for queue and raw port configuration information.

If not create a Local Port name the form \\remote\printer

You will most likely need to delete the port that was created when you made
the connection. It should have the print server device in the name.



--
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.

"riccume" <riccume@xxxxxx> wrote in message
news:E40C440A-3D30-47E7-AE16-9C0A3A7837E8@xxxxxx

Thank you Alan. Your suggestion to create a new local printer, local port,
\\NAS_name\printerserver seems to work! (I had tried this before, but either
used \\NAS_name\printers - the printer folder - or \\NAS_name\printers\lp -
the printer name - which generated an error). I'll let you know if I get any
problem (it worked once before, but then it stopped...) but for the moment
thanks a lot!!

"Alan Morris [MSFT]" wrote:

the network command

net view \\printservername

will display the verbiage of the share on these print server devices.

--
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.

"riccume" <riccume@xxxxxx> wrote in message
news041F167-BF62-45ED-894E-68971A35CEE8@xxxxxx

Printer continues to work, I think we can proclame the problem cured. Thanks
again Alan.

"Alan Morris [MSFT]" wrote:

The printer continues to work properly, I think we can now proclaim the
problem cured. Thanks a lot for your help Alan.

"Alan Morris [MSFT]" wrote: