Re: Access limitations(?), and moving to a simple LAN

Jeremy C B Nicoll wrote:

> I've no LAN yet, but yesterday (with Govind Kharbanda's help) connected
> my newish Iyonix (RO 5.09) to my RPC (RO 3.7), using one Cat5 cable.
> Access was enabled in both machines, and TCP/IP left turned off in both.
>
> When both machines were rebooted Access seemed to work ok from either
> machine.
>
> When we tried enabling TCP/IP in both machines (via Configure) with
> suitable definitions in place, both machines were able to ping the
> other. When we were doing this I removed my normal ANT Suite Internet
> stuff from the RPC's boot-up, so only the Configure definitions/
> processing were in place.
>
> But, although Access was turned on in both, and - on the surface
> appeared to work - eg a "Discs" icon was visible on both machines' icon
> bars, actually trying to use Access didn't work. The Iyonix couldn't
> see shares defined on the RPC. On the RPC we saw aborts, disappearance
> of the "Discs" icon
[snip]

Just wanted to clarify:

With TCP/IP disabled on both Iyo and RPC, Access worked fine.

With TCP/IP enabled on Iyo, but not on RPC, the Iyo's shared
"HardDisc4" was not visible on the RPC at all.

With TCP/IP enabled on both the Iyo (10.0.0.1) and the RPC (10.0.0.2),
the Iyo's shared "HardDisc4" was visible on the RPC. However any
attempt to mount the Iyo's HardDisc4 share on the RPC caused fatal
errors in ShareFS as Jeremy described.

Although we did successfully read the RPC's (multiple) shares on the
Iyo without TCP/IP turned on, I don't think we tried this after
re-enabling TCP/IP on both machines.

Govind

.

Relevant Pages