Hi
I'm a little unclear about which type of configuration your friend has,
and how you're going about diagnosing it.
Option 1: A Windows-only printer, shared out by Windows.
There's no IP address on the printer, so nothing to ping. Cheeck
share security as in option 3.
Option 2: A PostScript network printer, connected to Windows over IP, and
shared from Windows.
Why do it that way. you can connect to it directly from RISC OS,
using eg PS3 and free or proprietary network drivers (NetPrint for
example).
Option 3: A non-postscript network printer, with no RISC OS driver, shared
from Windows.
No alternative. However pinging from RISC OS doesn't tell you
much, even if it succeeds, which it ought to. My gut feeling is that the
change from Windows 10 to 11 has tightened up share security. Check the
permissions on the printer share within Windows. Check the username and
password in the connection, and look for that user on the share. It might
have been using "everyone" or "users", and that might have been removed.
Eventvwr might show security messages which could help. You need to log in
a Administrator to see those.
I can't try that here, as I don't have windows 11. No plans to "upgrade"
for reasons such as the above. If it ain't broke, I'm not going to fix it.
Alan
<snip>
> Yes, the friend has recently updated his Windows 10 to Windows 11 and for
> some reason, though his VRPC is working okay, his Printer RISC OS side
> which did work okay on Win 10, now doesn't seem to be communicating LAN
> wise to the Windows attached printer.
> From the RISC OS side I wanted him to Ping the Printer to see if there was
> any communication at all, but unfortunately he doesn't know the ip address
> of the printer, thus the 'arp' question.
> ATM. We are in a holding time as he's very busy with something else, but
> when his busy is done, I'll chat to him about how to finding the IP
> address of the printer Win side.
> TBH. As I know nothing about Win 11, I'm kind of peeing in the wind to see
> what returns. ;-)
> Dave
--
Alan Adams