🚀 go-pugleaf

Mike Oliphant a �crit dans le message <35D4F70F.8F039479@ibm.net>...

Thanks very much for your quick response

>Do the drivers load OK during boot? Both should give some confirmation of
this.
>Check your IBMLAN\IBMLAN.INI on both machines to make sure the domains are
the
>same. On one machine try NET SHARE CDRIVE=C:\, on the other try NET USE P:
>\\machine_name\CDRIVE, where machine_name is the name shown in the
IBMLAN.INI
>just above where you saw the domain name on the PC you are trying to
connect
>with.


I tried this and got what is now a familiar message for me:

NET3502: OS/2 error 53 has occurred.
SYS0053: The network path was not found.

>If you still can't connect, install TCPIP, give one machine address
10.2.1.1 and
>the other 10.2.1.2 with the netmask 255.255.255.0 and see if you can ping
one
>from the other. If not, see if you can ping a machine's own address (ie.
one the
>one with address 10.2.1.1 issue the command PING 10.2.1.1) and see if that
>works. If so, try it on the other machine too because such a local ping can
tell
>you whether there is a problem associated with the card or not. If both
cards
>come out OK, you are back to square one - trying to figure out what is
wrong
>with your peer.


I tried this too.  The local pings worked, but not those accross the
network.
I should add that both cards are Combo cards and I know they work via the
UTP plug as I have connected to the internet using both via a cable modem.
What I cannot be sure is whether the cards are now using the Coax port = is
a warm boot enough to get the 3c905 card to use its other exit plug?

Simon