Groups | Search | Server Info | Login | Register


Groups > comp.sys.acorn.networking > #5145

Re: Network devices

Newsgroups comp.sys.acorn.networking
References (2 earlier) <5b0d06141edave@triffid.co.uk> <15792d0d5b.chris@mytardis> <5b0d5ba35aDave@triffid.co.uk> <305b780d5b.chris@mytardis> <5b0d8ec58cdave@triffid.co.uk>
From Alan Adams <alan@adamshome.org.uk>
Date 2023-12-05 12:00 +0000
Organization Usenet.Farm
Subject Re: Network devices
Message-Id <e10efa0d5b.Alan@alan.adamshome.org.uk>

Show all headers | View raw


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

In message <5b0d8ec58cdave@triffid.co.uk>
          Dave <dave@triffid.co.uk> wrote:

<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

Back to comp.sys.acorn.networking | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Network devices Dave <dave@triffid.co.uk> - 2023-12-02 20:28 +0000
  Re: Network devices David Higton <dave@davehigton.me.uk> - 2023-12-02 22:05 +0000
    Network devices Dave <dave@triffid.co.uk> - 2023-12-03 15:14 +0000
      Re: Network devices Chris Hughes <news13@noonehere.co.uk> - 2023-12-03 22:24 +0000
        Re: Network devices Chris Newman <mec@npost.uk> - 2023-12-03 23:51 +0000
          Re: Network devices Dave <dave@triffid.co.uk> - 2023-12-04 06:58 +0000
          Re: Network devices Bob Latham <bob@sick-of-spam.invalid> - 2023-12-04 08:39 +0000
            Re: Network devices Dave <dave@triffid.co.uk> - 2023-12-04 15:53 +0000
              Re: Network devices Bob Latham <bob@sick-of-spam.invalid> - 2023-12-05 10:06 +0000
          Re: Network devices Richard Ashbery <basura@invalid.addr.uk> - 2023-12-04 12:16 +0000
            Re: Network devices Martin <News03@avisoft.f9.co.uk> - 2023-12-04 13:02 +0000
            Re: Network devices Chris Hughes <news13@noonehere.co.uk> - 2023-12-04 12:59 +0000
              Re: Network devices Richard Ashbery <basura@invalid.addr.uk> - 2023-12-04 17:57 +0000
              Re: Network devices Steve Fryatt <news@stevefryatt.org.uk> - 2023-12-04 18:04 +0000
            Re: Network devices Chris Newman <mec@npost.uk> - 2023-12-04 17:17 +0000
        Re: Network devices Dave <Dave@triffid.co.uk> - 2023-12-04 06:48 +0000
          Re: Network devices Chris Hughes <news13@noonehere.co.uk> - 2023-12-04 12:02 +0000
            Re: Network devices Dave <dave@triffid.co.uk> - 2023-12-04 16:07 +0000
              Re: Network devices Chris Hughes <news13@noonehere.co.uk> - 2023-12-04 16:40 +0000
              Re: Network devices Stuart <Spambin@argonet.co.uk> - 2023-12-04 21:15 +0000
              Re: Network devices Alan Adams <alan@adamshome.org.uk> - 2023-12-05 12:00 +0000
  Re: Network devices druck <news@druck.org.uk> - 2023-12-05 21:13 +0000

csiph-web