I finally installed W98SE on a NetVista 8364 [on a 4GB CF card]. It is wired to a WHR-G54S, it can transfer files via M$ Network Neighborhood, but it fails to connect past the upstairs router. I have a
760XL, also wired to the same WHR-G54S, that can get out to the internet just fine. So it appears the settings on the WHR-G54S are working.
The Netvista can ping the upstairs router at 192.168.1.2, but the ping times out for the downstairs router, 192.168.1.1, further, it can access the upper router via HTTPS inside of FireFox, but fails to resolve 192.68.1.1 Running WINIPCFG shows the downstairs router as the DHCP server. I see the Netvista is listed on the downstairs router as having a valid DHCP lease.
The 760XL can ping both the upstairs router (192.168.1.2) AND the downstairs router (192.168.1.1), and in addition, it can access both WHR-G54S via HTTPS.
Network properties for both systems are identical for TCP/IP. Went through them screen by screen. I'm stumped. I had three different systems wired to the upstairs router, and they all could access the internet. Now there is only this 760XL and the 8364.
It sounds to me like you may very well have two separate networks sharing the same IP network address space.
Unless you have done something in configuration to dumb down one of the two routers you have here into a switch and disabling one of the DHCP servers, your use of 192.168.1.x addresses for both routers is probably the reason you're seeing things breaking.
The upstairs router [192.168.1.2] has DHCP Server turned off. Again, this system [760XL] is plugged into the same router that the 8364 is plugged into. The 760XL gets through, the 8364 doesn't. Both systems upstairs are plugged into LAN ports, the single WAN port on the WHR-G54S has nothing plugged into it.
I finally noticed something running through IPCONFIG /ALL
Both systems are the same (except the 8364 uses an Intel PRO/100+ Management Adapter). The difference is that the 8364 says the Host Name is "NETVISTA", while the 760XL reports machine/ISP.
This is from the 760XL, which does get through to the downstairs router, and then to the internet: Windows 98 IP Configuration [for 760XL] Host Name . . . . . . . . . : 760XL.mad.wi.charter.com DNS Servers . . . . . . . . : 192.168.1.1 Node Type . . . . . . . . . : Broadcast NetBIOS Scope ID. . . . . . : IP Routing Enabled. . . . . : No WINS Proxy Enabled. . . . . : No NetBIOS Resolution Uses DNS : No
Before trying to unravel this, please draw an ascii diagram starting from your internet connection of what devices you have hanging off what ports and their ip's and what names you've been referring to them as. Please use manufacturer names and non names specific to your house.
I see mention of an upstairs router, a downstairs router, the wireless router, (one of these two may be the same device), one has a dhcp server disabled, not sure which is .1 and .2, and I'm only seeing one subnet mentioned throughout, and I suspect that'll lead us to why your network isn't happy.
Based on your ip config settings, I'd make sure that the router with ip of 192.168.1.1 is the one that has something connected to its WAN port and is the one serving up DHCP addresses.
I love ASCII art... 8364 (Netvista) Downstairs Upstairs --->192.168.1.128 WHR-G54S WHR-G54S | LAN Port ISP --> 192.168.1.1 (((((((((( 192.168.1.2 ----| DHCP Server DHCP Disabled | 760XL (760XL) --->192.168.1.105 LAN Port
NOTE: "((((" stands for wireless link. "----" stands for CAT5 cable Using DD-WRT, v23 SP2
formatting link
Both systems are the same (except the 8364 uses an Intel PRO/100+ Management Adapter). The difference is that the 8364 says the Host Name is "NETVISTA", while the 760XL reports machine/ISP.
This is from the 760XL, which does get through to the downstairs router (192.168.1.1), and then to the internet: Windows 98 IP Configuration [for 760XL] Host Name . . . . . . . . . : 760XL.mad.wi.charter.com DNS Servers . . . . . . . . : 192.168.1.1 Node Type . . . . . . . . . : Broadcast NetBIOS Scope ID. . . . . . : IP Routing Enabled. . . . . : No WINS Proxy Enabled. . . . . : No NetBIOS Resolution Uses DNS : No
Thank you this paints the picture a lot more completely and accurately.
Knowing that you're running third party firmware sure helps too. :-)
formatting link
buried in there I saw
"BrainSlayer Forum Answer [1]
formatting link
(edited to enhance): Client Bridge mode will only work well with just one connected computer on the far end, due a limitation in the 802.11 protocol. If you want to bridge a full LAN you must use WDS. The problem is that the 802.11 protocol just supports one MAC address, but in a LAN there is the possibility for more than one MAC address. It may cause ARP table problems, if you connect more than one computer on the far end of a Client Bridge mode setup. Use standard AP mode, if using WDS."
Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.