WIn98se ICS odd timing/connect loss issues cropping up, still there after reinstall... advice ?

On 12 Mar 2007 07:25:11 GMT, (Mike) wrote:

5. Everything seemed to be running ok, I was a bit puzzled because before this is
where things started to go haywire. However, I checked network neighbourhood
properties and found the gateway entry on the RTL8029 wasnt set to anything,
so changed this to 10.1.1.1 and rebooted. This is when the net access went bad
and started doing the cycle thing. ie. Took about a min before I could ping dns,
then ok for a few mins, then off for a few mins etc etc, here is route table
when system in that problematic state.
(gateway_reboot.txt)
Network Address Netmask Gateway Address Interface Metric
0.0.0.0 0.0.0.0 10.1.1.1 10.1.1.5 1
0.0.0.0 0.0.0.0 10.1.1.1 192.168.0.1 1


This looks to be the source of the problem.

There should only be one default gateway on the hostpc. The first line
above is correct which is set on the onboard adaptor. Leave the
RTL8029 gateway blank which will remove the second line.

This won't affect the client routing.


Jim.

In article , says...
Network Address Netmask Gateway Address Interface Metric
0.0.0.0 0.0.0.0 10.1.1.1 10.1.1.5 1
0.0.0.0 0.0.0.0 10.1.1.1 192.168.0.1 1

This looks to be the source of the problem.

There should only be one default gateway on the hostpc. The first line
above is correct which is set on the onboard adaptor. Leave the
RTL8029 gateway blank which will remove the second line.

This won't affect the client routing.

Ah ha, I should have said that when I had the gateway clear on the RTL8029
the first time that the client PC didnt have any net access though could
see each others files without problem but couldnt ping the router from the
client or any net IP. But the host could ping the client. The sequence I
desribed was repeated on one occasion with the client tried a few times,
I just shortened it and checked it for purpose of brevity.

But all this time I had forgotten to set the static route in the router
after the initial partial success doh !

------------------------------------------------------------------------
So once that was in - everything works a treat ) ! I am now manically
happy all is going well, you have no idea what a relief as my client pcs
emails had accumulated and that is where I do most work from late at night
with heaps of odd tech sites I review etc sigh

The ping of my ISP dns from the client is around 20ms and on average the
same as from the host which is also going very smoothly. I just have to
limit the u/l bandwidth of uTorrent so it wont clog the output queue...

So I must say many thanks for your patience and accuracy, it has been a great
experience to follow your reasoning and become more acquatined with the issues
of networking in general and as relates specifically to my setup which I
think for as long as possible I will keep with 98se and resist as far as
possible to 'upgrade', thankyou


--

Now I will be looking at the simplest way to allow my son to dial into
my machine so he can get onto the net from his mothers place across town
during the week. So I have another learning curve there it seems, dial up
networking with 98se (i am told) is mostly straightforward with occasional
pitfalls but I have time to asses that.
ie I would be looking to have my son dial in on the same line I have adsl on,
but of course have a filter between the line and the dialup modem (netcom)
which I also understand wouldnt go any faster than 33K...

Some 2 years ago I tried a program called 'netfor2' for the host which worked
surprisingly well and allowed my lab laptop to have its own net access across
from my host pc and all connected through a simple 3 wire RS232, it didnt
allow shared file transfer just relayed internet requests. Something like
that which my son could have email and web access to would be ideal,



--
Regards
Mike
* VK/VL Commodore FuseRails that wont warp or melt with fuse failure indication
and now with auto 10-15 min timer for engine illumination option.
* VN, VP, VR Models with relay holder in progress.
* Twin Tyres to suit most sedans, trikes and motorcycle sidecars
http://niche.iinet.net.au

In article , says...
Network Address Netmask Gateway Address Interface Metric
0.0.0.0 0.0.0.0 10.1.1.1 10.1.1.5 1
0.0.0.0 0.0.0.0 10.1.1.1 192.168.0.1 1

This looks to be the source of the problem.

There should only be one default gateway on the hostpc. The first line
above is correct which is set on the onboard adaptor. Leave the
RTL8029 gateway blank which will remove the second line.

This won't affect the client routing.

Ah ha, I should have said that when I had the gateway clear on the RTL8029
the first time that the client PC didnt have any net access though could
see each others files without problem but couldnt ping the router from the
client or any net IP. But the host could ping the client. The sequence I
desribed was repeated on one occasion with the client tried a few times,
I just shortened it and checked it for purpose of brevity.

But all this time I had forgotten to set the static route in the router
after the initial partial success doh !

------------------------------------------------------------------------
So once that was in - everything works a treat ) ! I am now manically
happy all is going well, you have no idea what a relief as my client pcs
emails had accumulated and that is where I do most work from late at night
with heaps of odd tech sites I review etc sigh

The ping of my ISP dns from the client is around 20ms and on average the
same as from the host which is also going very smoothly. I just have to
limit the u/l bandwidth of uTorrent so it wont clog the output queue...

So I must say many thanks for your patience and accuracy, it has been a great
experience to follow your reasoning and become more acquatined with the issues
of networking in general and as relates specifically to my setup which I
think for as long as possible I will keep with 98se and resist as far as
possible to 'upgrade', thankyou


--

Now I will be looking at the simplest way to allow my son to dial into
my machine so he can get onto the net from his mothers place across town
during the week. So I have another learning curve there it seems, dial up
networking with 98se (i am told) is mostly straightforward with occasional
pitfalls but I have time to asses that.
ie I would be looking to have my son dial in on the same line I have adsl on,
but of course have a filter between the line and the dialup modem (netcom)
which I also understand wouldnt go any faster than 33K...

Some 2 years ago I tried a program called 'netfor2' for the host which worked
surprisingly well and allowed my lab laptop to have its own net access across
from my host pc and all connected through a simple 3 wire RS232, it didnt
allow shared file transfer just relayed internet requests. Something like
that which my son could have email and web access to would be ideal,



--
Regards
Mike
* VK/VL Commodore FuseRails that wont warp or melt with fuse failure indication
and now with auto 10-15 min timer for engine illumination option.
* VN, VP, VR Models with relay holder in progress.
* Twin Tyres to suit most sedans, trikes and motorcycle sidecars
http://niche.iinet.net.au

On 12 Mar 2007 16:01:39 GMT, (Mike) wrote:


So I must say many thanks for your patience and accuracy, it has been a great
experience to follow your reasoning and become more acquatined with the issues
of networking in general and as relates specifically to my setup which I
think for as long as possible I will keep with 98se and resist as far as
possible to 'upgrade', thankyou



You are welcome.



Now I will be looking at the simplest way to allow my son to dial into
my machine so he can get onto the net from his mothers place across town
during the week. So I have another learning curve there it seems, dial up
networking with 98se (i am told) is mostly straightforward with occasional
pitfalls but I have time to asses that.
ie I would be looking to have my son dial in on the same line I have adsl on,
but of course have a filter between the line and the dialup modem (netcom)
which I also understand wouldnt go any faster than 33K...


You should be able to you use the dialup server which comes with
win98. You will get more flexibility by putting the remote machine(s)
on a different subnet just like you have with your own clientpc

This subject cropped up some time ago in another short thread which I
tracked down in the google archives. Although it used the NT remote
access service rather than the win98 DUN server the principle is the
same so the thread will be worth a read.
http://preview.tinyurl.com/25ny8h
http://tinyurl.com/25ny8h


Regards


Jim.

On 12 Mar 2007 16:01:39 GMT, (Mike) wrote:


So I must say many thanks for your patience and accuracy, it has been a great
experience to follow your reasoning and become more acquatined with the issues
of networking in general and as relates specifically to my setup which I
think for as long as possible I will keep with 98se and resist as far as
possible to 'upgrade', thankyou



You are welcome.



Now I will be looking at the simplest way to allow my son to dial into
my machine so he can get onto the net from his mothers place across town
during the week. So I have another learning curve there it seems, dial up
networking with 98se (i am told) is mostly straightforward with occasional
pitfalls but I have time to asses that.
ie I would be looking to have my son dial in on the same line I have adsl on,
but of course have a filter between the line and the dialup modem (netcom)
which I also understand wouldnt go any faster than 33K...


You should be able to you use the dialup server which comes with
win98. You will get more flexibility by putting the remote machine(s)
on a different subnet just like you have with your own clientpc

This subject cropped up some time ago in another short thread which I
tracked down in the google archives. Although it used the NT remote
access service rather than the win98 DUN server the principle is the
same so the thread will be worth a read.
http://preview.tinyurl.com/25ny8h
http://tinyurl.com/25ny8h


Regards


Jim.