RC4 won't connect to Internet

I have RC4 installed in its own little partition. Two glitches.

1) A Minor oddity - if I have the receiver for my wireless mouse in its 
USB slot the boot hangs just after the SnapGraphics logo appears. Remove 
the receiver, the boot goes through fine.

2) A Major problem - Thunderbird and Firefox can't communicate to the 
outside via my DSL hookup. As far as I can tell the TCP/IP and MPTS 
settings are identical with those in (e.g.) the RC1 installation from 
which I am sending this. I have run the NIC.CMD program, and the RealTek 
card and proper nic files are installed. But T'bird "can't reach the 
server 'pop-server (etc)' " where my email messages reside. Likewise 
FireFox "can't find the [mozilla] URL". Any suggestions on how to 
troubleshoot this problem?

TIA
Clyde

Clyde Stauffer wrote:

> I have RC4 installed in its own little partition. Two glitches.
> 
> 1) A Minor oddity - if I have the receiver for my wireless mouse in its
> USB slot the boot hangs just after the SnapGraphics logo appears. Remove
> the receiver, the boot goes through fine.
> 
> 2) A Major problem - Thunderbird and Firefox can't communicate to the
> outside via my DSL hookup. As far as I can tell the TCP/IP and MPTS
> settings are identical with those in (e.g.) the RC1 installation from
> which I am sending this. I have run the NIC.CMD program, and the RealTek
> card and proper nic files are installed. But T'bird "can't reach the
> server 'pop-server (etc)' " where my email messages reside. Likewise
> FireFox "can't find the [mozilla] URL". Any suggestions on how
to
> troubleshoot this problem?

Clyde, can you communicate with the DSL modem and/or router?  How about any
other machines that are hooked up?

Try using iptrace to monitor the interface and see if anything is being
passed - that's the first step.  Once you can verify that you are in fact
sending anything to the network we have something to work with.

-- 

Hi Clyde

Clyde Stauffer wrote:
> I have RC4 installed in its own little partition. Two glitches.
> 
> 1) A Minor oddity - if I have the receiver for my wireless mouse in its 
> USB slot the boot hangs just after the SnapGraphics logo appears. Remove 
> the receiver, the boot goes through fine.
>


Can you plug the receiver in and use the mouse after booting?



> 2) A Major problem - Thunderbird and Firefox can't communicate to the 
> outside via my DSL hookup. As far as I can tell the TCP/IP and MPTS 
> settings are identical with those in (e.g.) the RC1 installation from 
> which I am sending this. I have run the NIC.CMD program, and the RealTek 
> card and proper nic files are installed. But T'bird "can't reach the 
> server 'pop-server (etc)' " where my email messages reside. Likewise 
> FireFox "can't find the [mozilla] URL". Any suggestions on how to

> troubleshoot this problem?
> 
> TIA
> Clyde
> 



Does the nic driver load?

Compare the RC4 \MPTN\bin\setup.cmd file with that in RC1 to see if 
there is any difference - my guess is that you need the RC4 file to be 
the same as the RC1 file.

Regards

Clyde Stauffer wrote:

> Will Honea wrote:
> 
> 
>> Clyde, can you communicate with the DSL modem and/or router?  How
about
>> any other machines that are hooked up?
> 
>> Try using iptrace to monitor the interface and see if anything is
being
>> passed - that's the first step.  Once you can verify that you are in
fact
>> sending anything to the network we have something to work with.
> 
> Tried it on J: (the problem volume) and got not return. Tried the same
> program on E: (this volume, that communicates) and got messages about
> contacting 127.0.0.1. So apparently the J: volume is not seeing the
> router.
> 
> Suggestions for the next thing to try?

From the command line, run "netstat -r". Include the results and the
contents of \ibmcom\lantran.log.  That will reveal just how far the setup
is getting.

You've got me confused with your reference to volumes - are you saying that
you have 2 copies installed and booted between them?

-- 

Will Honea wrote:


> Clyde, can you communicate with the DSL modem and/or router?  How about
any
> other machines that are hooked up?

> Try using iptrace to monitor the interface and see if anything is being
> passed - that's the first step.  Once you can verify that you are in fact
> sending anything to the network we have something to work with.

Tried it on J: (the problem volume) and got not return. Tried the same 
program on E: (this volume, that communicates) and got messages about 
contacting 127.0.0.1. So apparently the J: volume is not seeing the router.

Suggestions for the next thing to try?

Clyde