Re: Access limitations(?), and moving to a simple LAN
- From: Tim Powys-Lybbe <tim@xxxxxxxxx>
- Date: Mon, 10 Oct 2005 11:02:40 +0100
In message of 9 Oct, Jeremy C B Nicoll <Jeremy@xxxxxxxxxxxxxxxx> wrote:
<snip>
> [ I must admit I'm confused about which of the RComp packages I need -
> is there some software needed to manage the broadband connection as
> well?
No.
> Eg, is !Netfetch necessary?
No.
> Or is it "just" a bundling of POPstar, Newshound etc -
Yes plus a control system for doing their configurations. Most people
find it very useful.
> I'd rather have separate apps and learn how they fit together, I
> think.
Personally I agree with you. But you then have to edit some of the
Choices files by hand and you have to read the separate help texts for
POPstar, Newshound, etc.
> I think I'll stick to Pluto as a news/mail client.]
Each to his own choices.
>
> > My Iyonix and RPC are connected on a local network to a broadband
> > router, and sharing discs via access. Occationally I run !DialUp on
> > the Risc PC to log in to my backup ISPs network so that the account
> > stays alive. So all you want to do is possible.
>
> Good!
>
> Since writing that lot last night, I've experimented a bit more. The
> ShareFS problem on the RPC is consistent. I set up a share of one of
> the RPC's disks, then select-click on "Disks" to get the filer view
> window, which shows that disk available. Click that and the disk's
> shared icon arrives on the icon bar. Click that and I get an error
> box and the shared disk icon I just clicked on vanishes from the icon
> bar (and isn't replaced by the Disks one). Reporter shows:
>
> 22:54:26.41 [IDEFSFiler\IDEFSFiler] Share IDEFS::Dug -protected
> 22:54:34.13 [ShareFS\ShareFS] Filer_OpenDir Resources:$.Discs 200 300
> -LargeIcons
> 22:54:39.01 ** WimpError ** from ShareFS
> Error : &00000298
> Message: Illegal task handle
> 22:54:39.01 [ShareFS\ShareFS] Exec
>
Have you set up Obey files on each machine to rename the share name of
its hard disc? If you are trying to share discs with the same name,
you will get into trouble.
> I've got each machine connected to a switch, and I've plugged the
> router into the switch as well.
>
> My router comes with address 192.168.1.1 so I've changed the IP
> addresses of both machines. The hosts files on each now contain:
>
> 192.168.1.1 router
> 192.168.1.101 iyonix
> 192.168.1.201 riscpc
> 192.168.1.255 jnall
>
> and from each machine I can ping all three devices. When I use the
> broadcast address the response from ping is a bit puzzling:
(pass)
What you are trying to do is entirely possible. It works here with an
Iyo, two RPCs, two PCs and a Mac (plus a print server and the second
PC is on a wireless link).
--
Tim Powys-Lybbe tim@xxxxxxxxx
For a miscellany of bygones: http://powys.org
.
- Follow-Ups:
- Re: Access limitations(?), and moving to a simple LAN
- From: Jeremy C B Nicoll
- Re: Access limitations(?), and moving to a simple LAN
- References:
- Access limitations(?), and moving to a simple LAN
- From: Jeremy C B Nicoll
- Re: Access limitations(?), and moving to a simple LAN
- From: druck
- Access limitations(?), and moving to a simple LAN
- From: Jeremy C B Nicoll
- Access limitations(?), and moving to a simple LAN
- Prev by Date: Re: Access limitations(?), and moving to a simple LAN
- Next by Date: Re: Access limitations(?), and moving to a simple LAN
- Previous by thread: Re: Access limitations(?), and moving to a simple LAN
- Next by thread: Re: Access limitations(?), and moving to a simple LAN
- Index(es):
Relevant Pages
|
