Groups | Search | Server Info | Login | Register

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

Re: Network devices

Show all headers | View raw

In article <305b780d5b.chris@mytardis>,
   Chris Hughes <news13@noonehere.co.uk> wrote:
> In message <5b0d5ba35aDave@triffid.co.uk>
>           Dave <Dave@triffid.co.uk> wrote:

> > In article <15792d0d5b.chris@mytardis>,
> >    Chris Hughes <news13@noonehere.co.uk> wrote:

> > [Snip]

> >> Correct it will not work on VRPC as all the networking is provided by
> >> the Windows side and passed through to the VRPC program side (Remember
> >> as far as Windows is concerned its just another application)

> >> Try it instead on the windows side in a command window, I think it
> >> should work (not got my PC on to double check at moment)

> > Thanks for the thoughts Chris.

> > I have no problem with the arp +flags command windows side, but this
> > "thing" I'm trying to sort for a friend is specifically a RISC OS
> > thing.

> Can you give us any details of this 'issue'?

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

-- 

Dave Triffid

Back to comp.sys.acorn.networking | Previous | Next — Previous 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