View Single Post
Old 11th-September-2005, 02:58 PM   #3 (permalink)
Clive Long
Registered User
 
Clive Long's Avatar
 
Join Date: Jan 2005
Location: London-innit
Posts: 1,465
Status: No Status
Rep Power: 3 Clive Long is a name known to allClive Long is a name known to allClive Long is a name known to allClive Long is a name known to allClive Long is a name known to allClive Long is a name known to allClive Long is a name known to allClive Long is a name known to allClive Long is a name known to allClive Long is a name known to all
Re: Maddening problem trying to configure Buffalo broadband / wireless router

Quote:
Originally Posted by El Salsero Gringo
Unplug the router from the ADSL line.
switch off the second PC.
disable the wireless adapter in the PC.
Yep did that - just using UTP - removed wireless from the equation
Quote:
Originally Posted by El Salsero Gringo
Set the pc's UTP port to "obtain an IP address automatically"
Well maybe - I tried both static IP address allocation and DHCP on the PC.
Same behaviour i.e. cannot ping nor http to router.
Maybe the router is setup to not respond to ICMP on the LAN side? Seems possible but unnecessary.
Quote:
Originally Posted by El Salsero Gringo
restart the router
Yep, yep, done several times
Quote:
Originally Posted by El Salsero Gringo
open a cmd window on the pc and type "ipconfig /renew" (alternatively reboot it if you prefer)
OK - will try that by setting XP to get IP from the "router" (I hate the abuse of that word) DHCP
Quote:
Originally Posted by El Salsero Gringo
See if you are assigned an IP address by the router - which will a) be proof the thing hasn't gone FUCT and b) give you an idea of what it thinks its own IP address is.
Now this is a bit interesting - when PC is rebooted, and look at ipconfig - she sees that XP wireless i/face has been assigned address 192.168.1.2 - which makes me feel that the PC is reaching the router and also getting an IP Address via DHCP - if only on the wireless interface.

However, the router doesn't respond to PING nor IE opening http://192.168.1.1 from the PC - that's the blocker.

I read that Symantec NIS - and the wonderful XP firewall can get in the way of outbound pings from the PC so she has uninstalled NIS for now (we'll reinstall NIS once the router is configured and connected on ADSL). We have switched off the XP firewall for now.

She will probably eventually run with firewall on the router.
Quote:
Originally Posted by El Salsero Gringo
If that doesn't work, see if there's a reset port, or a "global nuclear reset to factory settings" for the router.
Yep, done that a couple of times - using the instructions exactly as it said on the tin - during this sorry tale.
Quote:
Originally Posted by El Salsero Gringo
Don't bother about the ADSL line until you can get at least as far as getting an IP address from the router; ditto don't bother with the wireless.
Agreed, agreed. Step 1 is to connect PC to router over UTP. We are stuck at step 1.

There is the option to connect PC to router over USB - but you need a specific driver for that - how do you get it? That's right - download from their Website. That would be funny if it wasn't so pathetic.

Never had this with my Netgear.
Quote:
Originally Posted by El Salsero Gringo
Post again if there's any progress.
Unfortunately none.
My friend wants to phone Dell. I said yes - but be prepared to lose a day of her life as they read the standard scripts then say then problem is with the Buffalo - cue finger-pointing.

Hmmmmmmmmm ......
Clive Long is offline   Reply With Quote