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

Hullo all,

Have had win98se with ICS working fine for a couple of years at least but
since a reinstall/re-enable of ICS it has been acting a bit weird...

a. DHCP wont work anymore for the client computer
ie Client is not able to get an address from the Hosts DHCP, so I
have fixed it at 192.168.0.2 with mask 255.255.255.0
b. The client cycles each 10mins or so of internet connectivity
ie. After a boot up, the client is ok for about 10 mins then for
another 10mins or so cant do any net access then it comes back again
for a few mins then off again. A ping -t of my ISP's DNS shows
slow access of from 200 - 1000ms or more then timeouts then access is
back again, doesnt correlate with website or emails etc This is now the
continuous mode and is very frustrating !
c. The host PC is also having cycling issues but not nearly as bad as above.
Each 20mins or so it doesnt do any bit torrent uploads for about a min
then its ok again and although not as regular as the client the host has
a rough cycle of 15 to 20min uploads then 30 sec to 1min of stall.
Other net acess at the time seems ok on the host.
d. Cant ping the modem from the client, ie 10.1.1.1 comes with timeout always
but can ping 192.168.0.1 and 10.1.1.2 always but not always able to ping
the ISP DNS or other net addresses due to the cycling described in b.
e. Can always ping the client ok from the host
f. Have the port forward done ok in ICS so uTorrent is ok etc


Here are the IP addresses:-

10.1.1.1 dsl-502t on host with latest firmware
10.1.1.2 Host pc
192.168.0.1 Host PC lan card rtl8029as (coax 10baset)
192.168.0.2 Client PC on 10baset lan card rtl8029as

Have done the usual re-install and my route table on the host is:-
(not that I fully understand it, hence my paste here for advice?)


Network Address Netmask Gateway Address Interface Metric
0.0.0.0 0.0.0.0 10.1.1.1 10.1.1.2 1
0.0.0.0 0.0.0.0 10.1.1.1 10.1.1.2 1
10.0.0.0 255.0.0.0 10.1.1.2 10.1.1.2 1
10.0.0.0 255.0.0.0 10.1.1.2 10.1.1.2 1
10.1.1.2 255.255.255.255 127.0.0.1 127.0.0.1 1
10.255.255.255 255.255.255.255 10.1.1.2 10.1.1.2 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.0.0.0 255.0.0.0 192.168.0.1 192.168.0.1 1
192.168.0.1 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.0.255 255.255.255.255 192.168.0.1 192.168.0.1 1
224.0.0.0 224.0.0.0 192.168.0.1 192.168.0.1 1
224.0.0.0 224.0.0.0 10.1.1.2 10.1.1.2 1
224.0.0.0 224.0.0.0 10.1.1.2 10.1.1.2 1
255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1 1



What can I do to make this work properly as the cards seem fine when driven
from their test programs and file transfers are ok at 1333Kbits/sec between
host and clients etc

And its odd I cannot ping 10.1.1.1 from the client at all ? sigh

--
Regards
Mike
* GMC/GMH VK/VL FuseRails that wont warp or melt with fuse failure indication
and now with auto 10-15 min timer for engine illumination option.
* Australian 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 09 Mar 2007 04:53:24 GMT, (Mike) wrote:

Hullo all,

Have had win98se with ICS working fine for a couple of years at least but
since a reinstall/re-enable of ICS it has been acting a bit weird...

snip

Here are the IP addresses:-

10.1.1.1 dsl-502t on host with latest firmware


The dsl-502t is a router with its own nat sharing capability so you
should *NOT* be using ICS on win98se. This would cause all sorts of
problems not least of which is conflicting dhcp servers.

Disable ICS, reset the computers to use dhcp to get their addresses
and if everything isn't back to normal then post in detail how all
your kit is connected together and someone will be able to tell you
where you're going wrong.


Jim.

On 09 Mar 2007 04:53:24 GMT, (Mike) wrote:

Hullo all,

Have had win98se with ICS working fine for a couple of years at least but
since a reinstall/re-enable of ICS it has been acting a bit weird...

snip

Here are the IP addresses:-

10.1.1.1 dsl-502t on host with latest firmware


The dsl-502t is a router with its own nat sharing capability so you
should *NOT* be using ICS on win98se. This would cause all sorts of
problems not least of which is conflicting dhcp servers.

Disable ICS, reset the computers to use dhcp to get their addresses
and if everything isn't back to normal then post in detail how all
your kit is connected together and someone will be able to tell you
where you're going wrong.


Jim.

In article , says...

The dsl-502t is a router with its own nat sharing capability so you
should *NOT* be using ICS on win98se. This would cause all sorts of
problems not least of which is conflicting dhcp servers.

my dsl-502t has one usb and one utp connection and I am only using
the utp to connect to my host pc. dhcp is disabled in the 502
and the PC's ip of 10.1.1.2 is set manually.

Disable ICS, reset the computers to use dhcp to get their addresses
and if everything isn't back to normal then post in detail how all
your kit is connected together and someone will be able to tell you
where you're going wrong.

If I disable ICS then the client pc has no access at all.

Config is this:-
adsl into 502t with utp to the host motherboard lan connection
host also has an rtl8029 card with coax cabled to the client with
the same type of card.

As I mentioned, its been working fine for 2+ years, only recently
have odd slowdowns occured even after reinstall



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

The dsl-502t is a router with its own nat sharing capability so you
should *NOT* be using ICS on win98se. This would cause all sorts of
problems not least of which is conflicting dhcp servers.

my dsl-502t has one usb and one utp connection and I am only using
the utp to connect to my host pc. dhcp is disabled in the 502
and the PC's ip of 10.1.1.2 is set manually.

Disable ICS, reset the computers to use dhcp to get their addresses
and if everything isn't back to normal then post in detail how all
your kit is connected together and someone will be able to tell you
where you're going wrong.

If I disable ICS then the client pc has no access at all.

Config is this:-
adsl into 502t with utp to the host motherboard lan connection
host also has an rtl8029 card with coax cabled to the client with
the same type of card.

As I mentioned, its been working fine for 2+ years, only recently
have odd slowdowns occured even after reinstall



--
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 09 Mar 2007 06:20:06 GMT, (Mike) wrote:

If I disable ICS then the client pc has no access at all.

Config is this:-
adsl into 502t with utp to the host motherboard lan connection
host also has an rtl8029 card with coax cabled to the client with
the same type of card.

Okay.

If you can afford it then the best solution would be to get a switch
and plug all three devices into it.

There is a solution using your existing kit but it requires a bit more
configuration. You need the host to be a router but not a nat (ics)
router.

So first of all, disable ICS.

Then, enable routing in the registry as follows

System Key:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\VxD\MSTCP]
Value Name: EnableRouting
Data Type: (string value)
Value Data: (0 = disabled, 1 = enabled)

Then using the ip addresses from your first post.

Router
10.1.1.1
add static route to send traffic for network 192.168.0.0 via 10.1.1.2

HostPC
10.1.1.2 connected to the router
192.168.0.1 connected to the client
default gateway 10.1.1.1
enable dns - nameservers as notified by your isp or 10.1.1.1

ClientPC
192.168.0.2
default gateway 192.168.0.1
enable dns - nameservers as notified by your isp or 10.1.1.1


Jim.

On 09 Mar 2007 06:20:06 GMT, (Mike) wrote:

If I disable ICS then the client pc has no access at all.

Config is this:-
adsl into 502t with utp to the host motherboard lan connection
host also has an rtl8029 card with coax cabled to the client with
the same type of card.

Okay.

If you can afford it then the best solution would be to get a switch
and plug all three devices into it.

There is a solution using your existing kit but it requires a bit more
configuration. You need the host to be a router but not a nat (ics)
router.

So first of all, disable ICS.

Then, enable routing in the registry as follows

System Key:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\VxD\MSTCP]
Value Name: EnableRouting
Data Type: (string value)
Value Data: (0 = disabled, 1 = enabled)

Then using the ip addresses from your first post.

Router
10.1.1.1
add static route to send traffic for network 192.168.0.0 via 10.1.1.2

HostPC
10.1.1.2 connected to the router
192.168.0.1 connected to the client
default gateway 10.1.1.1
enable dns - nameservers as notified by your isp or 10.1.1.1

ClientPC
192.168.0.2
default gateway 192.168.0.1
enable dns - nameservers as notified by your isp or 10.1.1.1


Jim.

In article , says...

If you can afford it then the best solution would be to get a switch
and plug all three devices into it.

mmmm, if I can just get back to what I had before then I would be happy,
even though my coax lan is only 10Meg, it worked perfectly for years
with the current hardware, and I was easily able to add runs to the coax
for 3 other PCs when my kids friends came over for a small lan game party,
thats what I liked about the coax - it just need me to add a piece of
coax and move the terminator - much easier than adding a hub and I didnt
mind it being half-duplex the games they play dont put much b/w need.

So I am guessing some config snafuuu has occured which doesnt get cleared
when doing a reinstall, maybe it writes to the eeprom on the network card
as well as some correlated setting in the modem making it cyclically kludge
from time to time...

There is a solution using your existing kit but it requires a bit more
configuration. You need the host to be a router but not a nat (ics)
router.

So first of all, disable ICS.

Ok I will give this a go, though I've never had to do any of the
registry changes before when setting up ICS some 10 times or so for
my systems over last 6 years for family and friends... Am I guessing
correctly I need to re-enable ICS after the procedure below ?

Please see my other queries below,


Then, enable routing in the registry as follows

System Key:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\VxD\MSTCP]
Value Name: EnableRouting
Data Type: (string value)
Value Data: (0 = disabled, 1 = enabled)

Then using the ip addresses from your first post.

Router
10.1.1.1
add static route to send traffic for network 192.168.0.0 via 10.1.1.2

Does this mean I need to use the DOS route command, there are so many
entries in that already I am not sure precisely of the format of the
route print in terms of what it displays for example and what syntax I
need to issue to make it add the static route you mention etc



HostPC
10.1.1.2 connected to the router
192.168.0.1 connected to the client
default gateway 10.1.1.1
enable dns - nameservers as notified by your isp or 10.1.1.1

Ok, this seems like what I already have but will check it thoroughly,


ClientPC
192.168.0.2
default gateway 192.168.0.1
enable dns - nameservers as notified by your isp or 10.1.1.1

Given I couldnt even ping 10.1.1.1 before (or rather after the ICS
was re-enabled) then assuming the host changes and "adding a static
route" as you advise above then I should be able to ping 10.1.1.1 thereafter,
which suggests my registry got gurgled...

Jim.

Thanks Jim,
I had wondered why Win98se needed icsmgr to run, as if its just a routing
issue and if it doesnt need to be re-enabled then would the routing just
do it - of course if it does then I guess that makes more sense but begs
the question why it worked fine for 2+ years without registry changes ?


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

If you can afford it then the best solution would be to get a switch
and plug all three devices into it.

mmmm, if I can just get back to what I had before then I would be happy,
even though my coax lan is only 10Meg, it worked perfectly for years
with the current hardware, and I was easily able to add runs to the coax
for 3 other PCs when my kids friends came over for a small lan game party,
thats what I liked about the coax - it just need me to add a piece of
coax and move the terminator - much easier than adding a hub and I didnt
mind it being half-duplex the games they play dont put much b/w need.

So I am guessing some config snafuuu has occured which doesnt get cleared
when doing a reinstall, maybe it writes to the eeprom on the network card
as well as some correlated setting in the modem making it cyclically kludge
from time to time...

There is a solution using your existing kit but it requires a bit more
configuration. You need the host to be a router but not a nat (ics)
router.

So first of all, disable ICS.

Ok I will give this a go, though I've never had to do any of the
registry changes before when setting up ICS some 10 times or so for
my systems over last 6 years for family and friends... Am I guessing
correctly I need to re-enable ICS after the procedure below ?

Please see my other queries below,


Then, enable routing in the registry as follows

System Key:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\VxD\MSTCP]
Value Name: EnableRouting
Data Type: (string value)
Value Data: (0 = disabled, 1 = enabled)

Then using the ip addresses from your first post.

Router
10.1.1.1
add static route to send traffic for network 192.168.0.0 via 10.1.1.2

Does this mean I need to use the DOS route command, there are so many
entries in that already I am not sure precisely of the format of the
route print in terms of what it displays for example and what syntax I
need to issue to make it add the static route you mention etc



HostPC
10.1.1.2 connected to the router
192.168.0.1 connected to the client
default gateway 10.1.1.1
enable dns - nameservers as notified by your isp or 10.1.1.1

Ok, this seems like what I already have but will check it thoroughly,


ClientPC
192.168.0.2
default gateway 192.168.0.1
enable dns - nameservers as notified by your isp or 10.1.1.1

Given I couldnt even ping 10.1.1.1 before (or rather after the ICS
was re-enabled) then assuming the host changes and "adding a static
route" as you advise above then I should be able to ping 10.1.1.1 thereafter,
which suggests my registry got gurgled...

Jim.

Thanks Jim,
I had wondered why Win98se needed icsmgr to run, as if its just a routing
issue and if it doesnt need to be re-enabled then would the routing just
do it - of course if it does then I guess that makes more sense but begs
the question why it worked fine for 2+ years without registry changes ?


--
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 09 Mar 2007 11:27:44 GMT, (Mike) wrote:


So first of all, disable ICS.

Ok I will give this a go, though I've never had to do any of the
registry changes before when setting up ICS some 10 times or so for
my systems over last 6 years for family and friends... Am I guessing
correctly I need to re-enable ICS after the procedure below ?

No. This procedure doesn't use ICS. Editing the registry as described
enables routing without enabling ICS. Your router will be doing the
address translation (sharing) far more efficiently than ICS.


Please see my other queries below,


Then, enable routing in the registry as follows

System Key:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\VxD\MSTCP]
Value Name: EnableRouting
Data Type: (string value)
Value Data: (0 = disabled, 1 = enabled)

Then using the ip addresses from your first post.

Router
10.1.1.1
add static route to send traffic for network 192.168.0.0 via 10.1.1.2

Does this mean I need to use the DOS route command, there are so many
entries in that already I am not sure precisely of the format of the
route print in terms of what it displays for example and what syntax I
need to issue to make it add the static route you mention etc


No. Your router will probably have a web interface for its
configuration. Look in the manual for setting up static routes via the
web interface. If you don't have the manual there is a pdf on the
d-link website.



HostPC
10.1.1.2 connected to the router
192.168.0.1 connected to the client
default gateway 10.1.1.1
enable dns - nameservers as notified by your isp or 10.1.1.1

Ok, this seems like what I already have but will check it thoroughly,


ClientPC
192.168.0.2
default gateway 192.168.0.1
enable dns - nameservers as notified by your isp or 10.1.1.1

Given I couldnt even ping 10.1.1.1 before (or rather after the ICS
was re-enabled) then assuming the host changes and "adding a static
route" as you advise above then I should be able to ping 10.1.1.1 thereafter,
which suggests my registry got gurgled...


Until you configure the router to forward replies via the "host" pc
then it cannot reply because it does not know where to send the
packets for the client pc.

(sidenote: if you were using ICS this wouldn't be necessary because as
far as the router is concerned everything is coming from the host pc)

Jim.

Thanks Jim,
I had wondered why Win98se needed icsmgr to run, as if its just a routing
issue and if it doesnt need to be re-enabled then would the routing just
do it - of course if it does then I guess that makes more sense but begs
the question why it worked fine for 2+ years without registry changes ?


You could do it using ics, but since the router is already doing the
address translation you would be building in a needless bottleneck
(doing the same translation operation twice).

Check the ping times when it's done. If the boys do Internet gaming
they will certainly notice a *BIG* difference.


Jim.