🚀 go-pugleaf

In article <6r4f0v$o6n$1@sol6.tvd.be>,
"Simon Hampton" <simon.hampton@tvd.be> wrote:

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

The message for SYS0053 reads:

SYS0053: The network path was not found.

EXPLANATION: The server that you specified does not exist or has not
been started.

ACTION: Do one of the following and retry the command:
o  Verify that you specified the path name correctly.
o  Verify that the server specified is started.

Contact your network administrator if you continue to have problems.

It means your computer can't see the other and could be caused by a 
set up or hardware problem.


>>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?

The above indicates a hardware problem.

-- 
E-mail jknott@ca.ibm.com
_________________________________________________________________________
The above opinions are my own and not those of ISM Corp., a subsidiary of
IBM Canada Ltd.