IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New So I presume you've power cycled the Westell.
Of course I'd test by putting a Linksys router between my system and the Westell and see if my computers can communicate, but then I've got those sitting on the shelf here.

If it is the Westell, and I've had provider supplied routers go insane on me, the problem is convincing the provider, and that's not easy. Sometimes a factory reset will fix the problem, but you have to know the things default IP address and exactly how it was set up (and how to do the factory reset).

Another thing I'd do immediately is set my computers to static IP, restart them and see if they can communicate. I never use dhcp on small networks except for notebooks that are carried around because static makes testing much easier.
[link|http://www.aaxnet.com|AAx]
New Good point on using a static IP.
I've had [link|http://z.iwethey.org/forums/render/content/show?contentid=284539|trouble with DHCP] on some of my boxes with Linux.

Cheers,
Scott.
     Help, I must be getting old - (jbrabeck) - (11)
         same subnet? - (boxley) - (4)
             Answers - (jbrabeck) - (3)
                 Maybe reboot? :-/ -NT - (Another Scott) - (2)
                     Many times. Next time with size 10 1/2. :-) -NT - (jbrabeck) - (1)
                         Same or mixed versions of doze? -NT - (bepatient)
         Is Windows firewall enabled? - (Andrew Grygus) - (4)
             More to add - (jbrabeck) - (3)
                 So I presume you've power cycled the Westell. - (Andrew Grygus) - (1)
                     Good point on using a static IP. - (Another Scott)
                 It may not provide that. - (bepatient)
         Motherboard NIC was bad - (jbrabeck)

Too bad dark languages rarely survive...
132 ms