If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#21
|
|||
|
|||
WIn98se ICS odd timing/connect loss issues cropping up, still there after reinstall... advice ?
|
#23
|
|||
|
|||
WIn98se ICS odd timing/connect loss issues cropping up, still there after reinstall... advice ?
In article , says...
(I actually uninstalled ICS and not just disabled it - was that an error ?) But the registry key was already set to enable btw and it still is... I think that's okay. If you eventually do a clean install you will have to make the registry change. Routing is off by default. After a clean install (see comments at end) the key is not there at all, should I enter it manually and if so what other corresponding key should be present if any ? I'm fairly sure your router is working fine and the hostpc has its knickers in a twist. Thats what I was thinking but, the firmware version for the dsl-502t has been updated a couple of times, one release note indicate due to p2p issues. Now I'm not sure the latest version is stable as, on reflection, the problems have arisen since the last firmware upgrade, though its been on the site for a while. I cant go back to the old version because the modem's firmware update interface is broken and although I have the correct file from the web page and it was the previous one updated some time ago it says "The update file you chosed is incorrect." and the broken english in the error report doesnt inspire confidence. went back to modem web interface and then to tools and their ping function and although the host got timeouts the modem's ping tool never did ! More evidence in favour of zapping the hostpc The host pc certainly needed it anyway as it was over a year since the last reinstall and probably due for it, see notes later. If you eventually need to do this, ensure you don't carry over any registry corruption by following this procedure : Yes good point, learned that early on, plus also good to remove the r???.cab files in the sysbackup and I also get rid of system.1st (maybe?). Somehow the first time I tried a clean install but didnt get rid of the sysbackup, I had my old registry settings come back, even in a new directory (WIN2 etc), quite puzzling as there shouldnt be any link to it... The modem has an entry for Lan clients and only have the host as the one lan client as its the only other thing on that UTP connection, I didnt add the other pc as the modem wont accept its IP (outside 10.1.1.2 - 10.1.1.254) and the route to it is through the os etc... I'm not sure what this setting is for, You need to look in the manual for this. Apparently not necessary unless port forwarding is selected from the 'server' rules, since I use uTorrent and want it to connect quickly Ive set this up and it wont do any port forwarding unless the "Lan clients" has the right entry. The question that arises, is that if I want port forwarding for the client then I will have to change addresses so they fit in the lan clients range up to 10.1.1.254 and whether it will work with the route enable you suggest because I think its only for connections on the UTP but who knows for sure, anyway least of my problems... Here's the update:- - Clean install with all the same hardware and a reset of modem results in problem still there, so I'm aghast thinking my modem has developed some weird fault since a firmware upgrade. - I remove the rtl8029 pci lan card and try again, - Voila ! I have net access almost immediately upon bootup - hooray. - Plug rtl8029 card back in, locate the realtek reset and config utility for the card which also has a full self test, with the card from dos, the utility self test and cycles report all ok no prob at all. - Restart windows and problem is back again, its as if the hostpc doesnt know where to get net access from, is it possible its trying the RTL8029 gives up and switches to the other lan interface. As there is no option in IE tools to select which LAN connection for the net I am wondering if, not having it explicitly set, that given the firmware upgrade for the 502T that windows cycles between both ethernet interfaces, possibly because the modem firmware has some sort of flakey ack bug ? - Anyway for moment I have gone to control panel/system and disabled the RTL8029 but left it plugged in and net access is ok, will find another card and try again later when I have more patience or just switch it to a different slot in case its some int/buffer conflict that doesnt show up otherwise. ie All reports in Control Panel/System show no problems... - Is it possible I have a wrong entry in the network neighbourhood for all this time that only just now, with all the other changes, becomes an issue, questions that arise for the "TCP/IP - Realtek RTL8029 PCI Ethernet NIC" :- Have set manual IP of 192.168.0.1 with mask of 255.255.255.0 Had gateway of 10.1.1.1 DNS enable comes up same as LAN to Modem and its Host=labtemp server 203.0.178.191 But, what I am not sure about is the "Allow Binding to ATM", what should this be and should the box "Set this protocol to the default protocol" be ticked (I had it as No and not ticked), Is there some inspection s/w tool that can show me where packets are supposed to be going or attempted etc So I can diagnose what is happening when the RTL8029 is enabled or some other thing I can check whilst I await reply from DLink ? Thanks for your help so far, I think I am almost there... -- 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 |
#24
|
|||
|
|||
WIn98se ICS odd timing/connect loss issues cropping up, still there after reinstall... advice ?
In article , says...
do happen to have MAC addressing enabled on the router ? (mine re-enables after a reset ) Cant see this in any of the menus except the DHCP and I have DHCP disabled and all addresses set manually. Should I maybe place the router MAC address in they network neighbourhood to "force" windows so it wont go off the rails in case there is some bug in the router code, ie As a work around if its a 'dont care', ie Can I set it so it becomes a dont care if everything should be working anyway ? -- 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 |
#25
|
|||
|
|||
WIn98se ICS odd timing/connect loss issues cropping up, still there after reinstall... advice ?
In article , says...
do happen to have MAC addressing enabled on the router ? (mine re-enables after a reset ) Cant see this in any of the menus except the DHCP and I have DHCP disabled and all addresses set manually. Should I maybe place the router MAC address in they network neighbourhood to "force" windows so it wont go off the rails in case there is some bug in the router code, ie As a work around if its a 'dont care', ie Can I set it so it becomes a dont care if everything should be working anyway ? -- 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 |
#26
|
|||
|
|||
WIn98se ICS odd timing/connect loss issues cropping up, still there after reinstall... advice ?
On 11 Mar 2007 20:43:26 GMT, (Mike) wrote: In article , says... (I actually uninstalled ICS and not just disabled it - was that an error ?) But the registry key was already set to enable btw and it still is... I think that's okay. If you eventually do a clean install you will have to make the registry change. Routing is off by default. After a clean install (see comments at end) the key is not there at all, should I enter it manually and if so what other corresponding key should be present if any ? Yes you have to enter it manually. If it isn't there at all it takes the default value (which is off). snip Here's the update:- - Clean install with all the same hardware and a reset of modem results in problem still there, so I'm aghast thinking my modem has developed some weird fault since a firmware upgrade. - I remove the rtl8029 pci lan card and try again, - Voila ! I have net access almost immediately upon bootup - hooray. What does your routing table say with this card enabled and then disabled? Any differences there might shed some light. snip But, what I am not sure about is the "Allow Binding to ATM", what should this be and should the box "Set this protocol to the default protocol" be ticked (I had it as No and not ticked), Don't know. 99.9% of the time these settings should be left as the installation default. Is there some inspection s/w tool that can show me where packets are supposed to be going or attempted etc So I can diagnose what is happening when the RTL8029 is enabled or some other thing I can check whilst I await reply from DLink ? Thanks for your help so far, I think I am almost there... If the routing table(s) don't throw up any clues then I can't think what the cause might be. It's not my field either so I can't recommend any utils. Jim. |
#27
|
|||
|
|||
WIn98se ICS odd timing/connect loss issues cropping up, still there after reinstall... advice ?
On 11 Mar 2007 20:43:26 GMT, (Mike) wrote: In article , says... (I actually uninstalled ICS and not just disabled it - was that an error ?) But the registry key was already set to enable btw and it still is... I think that's okay. If you eventually do a clean install you will have to make the registry change. Routing is off by default. After a clean install (see comments at end) the key is not there at all, should I enter it manually and if so what other corresponding key should be present if any ? Yes you have to enter it manually. If it isn't there at all it takes the default value (which is off). snip Here's the update:- - Clean install with all the same hardware and a reset of modem results in problem still there, so I'm aghast thinking my modem has developed some weird fault since a firmware upgrade. - I remove the rtl8029 pci lan card and try again, - Voila ! I have net access almost immediately upon bootup - hooray. What does your routing table say with this card enabled and then disabled? Any differences there might shed some light. snip But, what I am not sure about is the "Allow Binding to ATM", what should this be and should the box "Set this protocol to the default protocol" be ticked (I had it as No and not ticked), Don't know. 99.9% of the time these settings should be left as the installation default. Is there some inspection s/w tool that can show me where packets are supposed to be going or attempted etc So I can diagnose what is happening when the RTL8029 is enabled or some other thing I can check whilst I await reply from DLink ? Thanks for your help so far, I think I am almost there... If the routing table(s) don't throw up any clues then I can't think what the cause might be. It's not my field either so I can't recommend any utils. Jim. |
#28
|
|||
|
|||
WIn98se ICS odd timing/connect loss issues cropping up, still there after reinstall... advice ?
In article , says...
Yes you have to enter it manually. If it isn't there at all it takes the default value (which is off). ok, np, done that in sequence described later:- What does your routing table say with this card enabled and then disabled? Any differences there might shed some light. Ok Jim, Here is the sequence of changes with corresponding route tables and in all cases the client machine is off. I did change the PC ip address from 10.1.1.2 to 10.1.1.5 as this is the IP that dlink recommend when doing a firmware upgrade, so I did a firmware refresh of the dlink, re-entered all the settings, upnp is off, dhcp is off, lan client is 10.1.1.5, port forwarding of one port enabled, rebooted the modem and the pc and as it was working fine the router from this point on hasnt been touched and left running without any changes... 1. All net working ok, pings all ok, RTL8029as card installed but disabled (whenok.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 10.0.0.0 255.0.0.0 10.1.1.5 10.1.1.5 1 10.1.1.5 255.255.255.255 127.0.0.1 127.0.0.1 1 10.255.255.255 255.255.255.255 10.1.1.5 10.1.1.5 1 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 224.0.0.0 224.0.0.0 10.1.1.5 10.1.1.5 1 255.255.255.255 255.255.255.255 10.1.1.5 10.1.1.5 1 2. RTL8029as card enabled in win98 controlpanel/system, got hour glass of some activity but, pings all ok, not yet rebooted but route table had changed without having done a reboot. ie Hourglass signified some possible change, here is. (enabled.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 10.0.0.0 255.0.0.0 10.1.1.5 10.1.1.5 1 10.1.1.5 255.255.255.255 127.0.0.1 127.0.0.1 1 10.255.255.255 255.255.255.255 10.1.1.5 10.1.1.5 1 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.0.0 255.255.255.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 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.5 10.1.1.5 1 255.255.255.255 255.255.255.255 10.1.1.5 10.1.1.5 1 3. Rebooted to make sure any tendrils of enabling RTL8029 needed to filter through, pings to ISP dns came up straight away all ok. (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 10.0.0.0 255.0.0.0 10.1.1.5 10.1.1.5 1 10.1.1.5 255.255.255.255 127.0.0.1 127.0.0.1 1 10.255.255.255 255.255.255.255 10.1.1.5 10.1.1.5 1 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.0.0 255.255.255.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 10.1.1.5 10.1.1.5 1 224.0.0.0 224.0.0.0 192.168.0.1 192.168.0.1 1 255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1 1 4. Inserted reg entry to enable routing per your advice, saved copy and rebooted, net all ok, pings to ISP dns all ok. (enable_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 10.0.0.0 255.0.0.0 10.1.1.5 10.1.1.5 1 10.1.1.5 255.255.255.255 127.0.0.1 127.0.0.1 1 10.255.255.255 255.255.255.255 10.1.1.5 10.1.1.5 1 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.0.0 255.255.255.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 10.1.1.5 10.1.1.5 1 224.0.0.0 224.0.0.0 192.168.0.1 192.168.0.1 1 255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1 1 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 10.0.0.0 255.0.0.0 10.1.1.5 10.1.1.5 1 10.1.1.5 255.255.255.255 127.0.0.1 127.0.0.1 1 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.0.0 255.255.255.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 10.1.1.5 10.1.1.5 1 224.0.0.0 224.0.0.0 192.168.0.1 192.168.0.1 1 255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1 1 6. In the above state the net is almost unusable and unsatisfactory so I disabled the gateway for the RTL8029, rebooted and all net activity was ok again, pings to dns consistent, but leaves the RTL8029 without a gateway so possibly no client net access... Here is route table, gateway cleared, rebooted. (no_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 10.0.0.0 255.0.0.0 10.1.1.5 10.1.1.5 1 10.1.1.5 255.255.255.255 127.0.0.1 127.0.0.1 1 10.255.255.255 255.255.255.255 10.1.1.5 10.1.1.5 1 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.0.0 255.255.255.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 10.1.1.5 10.1.1.5 1 224.0.0.0 224.0.0.0 192.168.0.1 192.168.0.1 1 255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1 1 I notice the route table gets its entries moved around between reboots but does that matter since the numbers seem to be the same for the most part and I dont understand the differences though it seems a bit logical, I cant make sense of the extra entries that seem like padding and I wonder if the "Metric" isnt some priority issue - dont know ? Since changing the gateway in the RTL8029 config makes things go nuts.ie. Adding 10.1.1.1 makes it bad, then removing 10.1.1.1 makes it ok is pretty good evidence its not some other thing unless the router cant make sense of where its supposed to reply to requests ie. Is it possible its trying to send replies to the RTL8029 instead of the process that made the intial request, then here is all the entries for the network neighbourhood RTL8029 TCP/IP settings, should I choose a different gateway address perhaps, have I made a mask error etc ? IP Address / IP Specified 192.168.0.1 Mask 255.255.255.0 WINS Config/ Disable WINS Resolution Gateway/ none specified DNS Config/ Host = labtemp, no domain, one entry of 203.0.178.191 Bindings/ Client for Microsoft Networks ticked, file and print sharing unticked Advanced/ Allow Binding to ATM = no, default protocol box unticked Netbios/ I want to enable NETBIOS over TCP/IP, ticked and Grayed out FWIW, here are the settings for the LAN interface to the router via the motherboards on board lan (VIA VT6102 Rhine II Fast Ethernet Adapter) :- IP Address / IP Specified 10.1.1.5 Mask 255.0.0.0 WINS Config/ Disable WINS Resolution Gateway/ 10.1.1.1 DNS Config/ Host = labtemp, no domain, one entry of 203.0.178.191 Bindings/ Client for Microsoft Networks ticked, file and print sharing unticked Advanced/ Allow Binding to ATM = no, default protocol box is ticked this time ! Netbios/ I want to enable NETBIOS over TCP/IP, ticked and Grayed out The only other changes I did, which didnt affect anything was increase the buffers on the LAN interface to the router from 64 per transmit/receive to 128. I have 512Megs ram in the PC and think it can afford to allocate a bit more buffer space, this didnt change anything though... Sent a tech support email to Dlink last night describing issue as much as possible and referenced this newgroup and postings, no ack as yet, bit early I guess... -- 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 |
#29
|
|||
|
|||
WIn98se ICS odd timing/connect loss issues cropping up, still there after reinstall... advice ?
In article , says...
Yes you have to enter it manually. If it isn't there at all it takes the default value (which is off). ok, np, done that in sequence described later:- What does your routing table say with this card enabled and then disabled? Any differences there might shed some light. Ok Jim, Here is the sequence of changes with corresponding route tables and in all cases the client machine is off. I did change the PC ip address from 10.1.1.2 to 10.1.1.5 as this is the IP that dlink recommend when doing a firmware upgrade, so I did a firmware refresh of the dlink, re-entered all the settings, upnp is off, dhcp is off, lan client is 10.1.1.5, port forwarding of one port enabled, rebooted the modem and the pc and as it was working fine the router from this point on hasnt been touched and left running without any changes... 1. All net working ok, pings all ok, RTL8029as card installed but disabled (whenok.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 10.0.0.0 255.0.0.0 10.1.1.5 10.1.1.5 1 10.1.1.5 255.255.255.255 127.0.0.1 127.0.0.1 1 10.255.255.255 255.255.255.255 10.1.1.5 10.1.1.5 1 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 224.0.0.0 224.0.0.0 10.1.1.5 10.1.1.5 1 255.255.255.255 255.255.255.255 10.1.1.5 10.1.1.5 1 2. RTL8029as card enabled in win98 controlpanel/system, got hour glass of some activity but, pings all ok, not yet rebooted but route table had changed without having done a reboot. ie Hourglass signified some possible change, here is. (enabled.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 10.0.0.0 255.0.0.0 10.1.1.5 10.1.1.5 1 10.1.1.5 255.255.255.255 127.0.0.1 127.0.0.1 1 10.255.255.255 255.255.255.255 10.1.1.5 10.1.1.5 1 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.0.0 255.255.255.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 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.5 10.1.1.5 1 255.255.255.255 255.255.255.255 10.1.1.5 10.1.1.5 1 3. Rebooted to make sure any tendrils of enabling RTL8029 needed to filter through, pings to ISP dns came up straight away all ok. (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 10.0.0.0 255.0.0.0 10.1.1.5 10.1.1.5 1 10.1.1.5 255.255.255.255 127.0.0.1 127.0.0.1 1 10.255.255.255 255.255.255.255 10.1.1.5 10.1.1.5 1 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.0.0 255.255.255.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 10.1.1.5 10.1.1.5 1 224.0.0.0 224.0.0.0 192.168.0.1 192.168.0.1 1 255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1 1 4. Inserted reg entry to enable routing per your advice, saved copy and rebooted, net all ok, pings to ISP dns all ok. (enable_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 10.0.0.0 255.0.0.0 10.1.1.5 10.1.1.5 1 10.1.1.5 255.255.255.255 127.0.0.1 127.0.0.1 1 10.255.255.255 255.255.255.255 10.1.1.5 10.1.1.5 1 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.0.0 255.255.255.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 10.1.1.5 10.1.1.5 1 224.0.0.0 224.0.0.0 192.168.0.1 192.168.0.1 1 255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1 1 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 10.0.0.0 255.0.0.0 10.1.1.5 10.1.1.5 1 10.1.1.5 255.255.255.255 127.0.0.1 127.0.0.1 1 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.0.0 255.255.255.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 10.1.1.5 10.1.1.5 1 224.0.0.0 224.0.0.0 192.168.0.1 192.168.0.1 1 255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1 1 6. In the above state the net is almost unusable and unsatisfactory so I disabled the gateway for the RTL8029, rebooted and all net activity was ok again, pings to dns consistent, but leaves the RTL8029 without a gateway so possibly no client net access... Here is route table, gateway cleared, rebooted. (no_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 10.0.0.0 255.0.0.0 10.1.1.5 10.1.1.5 1 10.1.1.5 255.255.255.255 127.0.0.1 127.0.0.1 1 10.255.255.255 255.255.255.255 10.1.1.5 10.1.1.5 1 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.0.0 255.255.255.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 10.1.1.5 10.1.1.5 1 224.0.0.0 224.0.0.0 192.168.0.1 192.168.0.1 1 255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1 1 I notice the route table gets its entries moved around between reboots but does that matter since the numbers seem to be the same for the most part and I dont understand the differences though it seems a bit logical, I cant make sense of the extra entries that seem like padding and I wonder if the "Metric" isnt some priority issue - dont know ? Since changing the gateway in the RTL8029 config makes things go nuts.ie. Adding 10.1.1.1 makes it bad, then removing 10.1.1.1 makes it ok is pretty good evidence its not some other thing unless the router cant make sense of where its supposed to reply to requests ie. Is it possible its trying to send replies to the RTL8029 instead of the process that made the intial request, then here is all the entries for the network neighbourhood RTL8029 TCP/IP settings, should I choose a different gateway address perhaps, have I made a mask error etc ? IP Address / IP Specified 192.168.0.1 Mask 255.255.255.0 WINS Config/ Disable WINS Resolution Gateway/ none specified DNS Config/ Host = labtemp, no domain, one entry of 203.0.178.191 Bindings/ Client for Microsoft Networks ticked, file and print sharing unticked Advanced/ Allow Binding to ATM = no, default protocol box unticked Netbios/ I want to enable NETBIOS over TCP/IP, ticked and Grayed out FWIW, here are the settings for the LAN interface to the router via the motherboards on board lan (VIA VT6102 Rhine II Fast Ethernet Adapter) :- IP Address / IP Specified 10.1.1.5 Mask 255.0.0.0 WINS Config/ Disable WINS Resolution Gateway/ 10.1.1.1 DNS Config/ Host = labtemp, no domain, one entry of 203.0.178.191 Bindings/ Client for Microsoft Networks ticked, file and print sharing unticked Advanced/ Allow Binding to ATM = no, default protocol box is ticked this time ! Netbios/ I want to enable NETBIOS over TCP/IP, ticked and Grayed out The only other changes I did, which didnt affect anything was increase the buffers on the LAN interface to the router from 64 per transmit/receive to 128. I have 512Megs ram in the PC and think it can afford to allocate a bit more buffer space, this didnt change anything though... Sent a tech support email to Dlink last night describing issue as much as possible and referenced this newgroup and postings, no ack as yet, bit early I guess... -- 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 |
#30
|
|||
|
|||
WIn98se ICS odd timing/connect loss issues cropping up, still there after reinstall... advice ?
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
WinME Reinstall: Seek Advice on advisability doing this | BrianZ | General | 23 | January 31st 06 11:25 PM |
WinME Reinstall: Seek Advice on advisability doing this | BrianZ | Setup & Installation | 23 | January 31st 06 11:25 PM |
Format HD and reinstall 98SE-Advice sought | Blair | General | 2 | October 8th 04 06:25 AM |
Newbie wants advice on how to connect PC with print server. | John Kirton | Networking | 3 | July 12th 04 01:02 AM |