Networking Forums

Networking Forums > Wireless Networking > Wireless Internet > Buffalo WHR-G54S and W98SE issues (somewhat OT)

Reply
Thread Tools Display Modes

Buffalo WHR-G54S and W98SE issues (somewhat OT)

 
 
Louis Ohland
Guest
Posts: n/a

 
      03-21-2007, 06:27 PM
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.
 
Reply With Quote
 
 
 
 
Todd H.
Guest
Posts: n/a

 
      03-21-2007, 08:07 PM
Louis Ohland <(E-Mail Removed)> writes:

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


Assuming you're subnet mask is 255.255.255.0 ?

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.

Best Regards,
--
Todd H.
http://www.toddh.net/
 
Reply With Quote
 
Louis Ohland
Guest
Posts: n/a

 
      03-22-2007, 02:07 PM
Todd H. wrote:
> Louis Ohland <(E-Mail Removed)> writes:
>
>> 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.

>
> Assuming you're subnet mask is 255.255.255.0 ?


Yes. Subnet is the same for both systems.

> 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

0 Ethernet adapter :
Description . . . . . . . . : Belkin F5D5020 PCMCIA Card Network Card.
Physical Address. . . . . . : 00-XX-XX-XX-5F-F3
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 192.168.1.105
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . : 192.168.1.1
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . : 03 22 07 08:19:49
Lease Expires . . . . . . . : 03 23 07 08:19:49


This is from the confused system:
Windows 98 IP Configuration [for 760XL]
Host Name . . . . . . . . . : NETVISTA
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

0 Ethernet adapter :
Description . . . . . . . . : Intel PRO/100+ Management Adapter
Physical Address. . . . . . : 00-XX-XX-XX-8B-3A
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 192.168.1.128
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . : 192.168.1.1
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . : 03 22 07 08:39:52
Lease Expires . . . . . . . : 03 23 07 08:39:52

 
Reply With Quote
 
Louis Ohland
Guest
Posts: n/a

 
      03-22-2007, 02:12 PM
Louis Ohland wrote:
> This is from the confused system:
> Windows 98 IP Configuration [for 760XL]
> Host Name . . . . . . . . . : NETVISTA


Oops, should be:

This is from the confused system:
Windows 98 IP Configuration [for 8364]
Host Name . . . . . . . . . : NETVISTA
 
Reply With Quote
 
Todd H.
Guest
Posts: n/a

 
      03-22-2007, 03:01 PM
Louis Ohland <(E-Mail Removed)> writes:
> Todd H. wrote:
> > Louis Ohland <(E-Mail Removed)> writes:
> >
> >> 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.

> > Assuming you're subnet mask is 255.255.255.0 ?

>
> Yes. Subnet is the same for both systems.
>
> > 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.


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.

--
Todd H.
http://www.toddh.net/
 
Reply With Quote
 
Louis Ohland
Guest
Posts: n/a

 
      03-22-2007, 03:31 PM
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

http://www.gilanet.com/ohlandl/NIC/w...#Client_Bridge

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

0 Ethernet adapter :
Description . . . . . . . . : Belkin F5D5020 PCMCIA Card Network Card.
Physical Address. . . . . . : 00-XX-XX-XX-5F-F3
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 192.168.1.105
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . : 192.168.1.1
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . : 03 22 07 08:19:49
Lease Expires . . . . . . . : 03 23 07 08:19:49


This is from the confused system:
Windows 98 IP Configuration [for 8364]
Host Name . . . . . . . . . : NETVISTA
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

0 Ethernet adapter :
Description . . . . . . . . : Intel PRO/100+ Management Adapter
Physical Address. . . . . . : 00-XX-XX-XX-8B-3A
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 192.168.1.128
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . : 192.168.1.1
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . : 03 22 07 08:39:52
Lease Expires . . . . . . . : 03 23 07 08:39:52
 
Reply With Quote
 
Todd H.
Guest
Posts: n/a

 
      03-22-2007, 05:39 PM
Louis Ohland <(E-Mail Removed)> writes:

> 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


Thank you this paints the picture a lot more completely and
accurately.

> http://www.gilanet.com/ohlandl/NIC/w...#Client_Bridge


Knowing that you're running third party firmware sure helps too. :-)


> 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
>
> 0 Ethernet adapter :
> Description . . . . . . . . : Belkin F5D5020 PCMCIA Card Network Card.
> Physical Address. . . . . . : 00-XX-XX-XX-5F-F3
> DHCP Enabled. . . . . . . . : Yes
> IP Address. . . . . . . . . : 192.168.1.105
> Subnet Mask . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . : 192.168.1.1
> DHCP Server . . . . . . . . : 192.168.1.1
> Primary WINS Server . . . . :
> Secondary WINS Server . . . :
> Lease Obtained. . . . . . . : 03 22 07 08:19:49
> Lease Expires . . . . . . . : 03 23 07 08:19:49
>
>
> This is from the confused system:
> Windows 98 IP Configuration [for 8364]
> Host Name . . . . . . . . . : NETVISTA
> 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
>
> 0 Ethernet adapter :
> Description . . . . . . . . : Intel PRO/100+ Management Adapter
> Physical Address. . . . . . : 00-XX-XX-XX-8B-3A
> DHCP Enabled. . . . . . . . : Yes
> IP Address. . . . . . . . . : 192.168.1.128
> Subnet Mask . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . : 192.168.1.1
> DHCP Server . . . . . . . . : 192.168.1.1




http://www.dd-wrt.com/wiki/index.php/Wireless_Bridge

buried in there I saw

"BrainSlayer Forum Answer [1]
(http://www.dd-wrt.com/phpBB2/viewtopic.php?t=936) (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."



--
Todd H.
http://www.toddh.net/
 
Reply With Quote
 
Louis Ohland
Guest
Posts: n/a

 
      03-22-2007, 06:20 PM
Todd, I had three computers hooked up to this router before with the
same AP-Client Bridge and they ALL worked. NT 4, OS/2 Warp and W98SE.
When I have time, I can fire up the NT4 box and see what happens.

Todd H. wrote:
> "BrainSlayer Forum Answer [1]
> (http://www.dd-wrt.com/phpBB2/viewtopic.php?t=936) (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."
>
>
>

 
Reply With Quote
 
Todd H.
Guest
Posts: n/a

 
      03-22-2007, 07:25 PM
Louis Ohland <(E-Mail Removed)> writes:

> Todd, I had three computers hooked up to this router before with the
> same AP-Client Bridge and they ALL worked. NT 4, OS/2 Warp and
> W98SE. When I have time, I can fire up the NT4 box and see what
> happens.


I'm out.

--
Todd H.
http://www.toddh.net/
 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Buffalo WLI2-PCI-G54S and Netvista on Client Bridge oddities John Navas Wireless Internet 3 03-27-2007 03:56 AM
Running commentary on Buffalo WHR-G54S Louis Ohland Wireless Internet 19 11-28-2006 02:13 PM
Correct DD-WRT version for use with Buffalo WHR-G54S Louis Ohland Wireless Internet 2 11-25-2006 12:13 AM
Wireless between two Buffalo WHR-G54S Louis Ohland Wireless Internet 12 11-24-2006 11:33 PM
Buffalo Stampede! (WHR-G54S can't detect ISP) Louis Ohland Wireless Internet 5 11-18-2006 10:33 PM



1 2 3 4 5 6 7 8 9 10 11