router is end of life for tech support

  • Thread starter Thread starter hawat.thufir
  • Start date Start date
H

hawat.thufir

The router: SMC7004VWBR-CA

My connection is 802.11b/g, as is my neighbors. The landlord has a
wired connection. My old computer worked fine with this particular
router for a long time, but the new computer isn't "playing well" for
unknown reasons.
From the landlord (network admin):
Click to expand...

ipconfig/all

physical addres 00 0E A6 3C a8 4a

dhcp no
ip 192.168.2.182
subnet 255.255.255.0
default gateway 192.168.2.1
dns 64.59.144.16
64.59.144.17

ping reply bytes=32 time=1ms ttl=255

tracrt

1 1ms 2ms 1 ms 192.168.2.1

trace complete


We replaced the SMC router with a Linksys router, just for a test, and
things worked fine for me:


C:\>
C:\>
C:\>ipconfig /all


Windows 2000 IP Configuration


Host Name . . . . . . . . . . . . : geidiprime
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : vc.shawcable.net


Ethernet adapter Local Area Connection:


Connection-specific DNS Suffix . : vc.shawcable.net
Description . . . . . . . . . . . : Linksys Wireless-G USB
Network Adapt
er
Physical Address. . . . . . . . . : 00-16-B6-4E-99-55
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 64.59.144.92
64.59.144.93
Lease Obtained. . . . . . . . . . : Thursday, April 20, 2006
10:08:49 AM


Lease Expires . . . . . . . . . . : Friday, April 21, 2006
10:08:49 AM


C:\>ping 192.168.1.1


Pinging 192.168.1.1 with 32 bytes of data:


Reply from 192.168.1.1: bytes=32 time=10ms TTL=64
Reply from 192.168.1.1: bytes=32 time<10ms TTL=64
Reply from 192.168.1.1: bytes=32 time<10ms TTL=64
Reply from 192.168.1.1: bytes=32 time<10ms TTL=64


Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 10ms, Average = 2ms


C:\>




Of course, the routers have different IP ranges (192.168.2.1 for SMC,
192.168.1.1 for Linksys)


Here's my attempt to connect to the SMC router:


Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-1999 Microsoft Corp.

C:\>ipconfig /all


Windows 2000 IP Configuration


Host Name . . . . . . . . . . . . : geidiprime
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No


Ethernet adapter Local Area Connection:


Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Linksys Wireless-G USB
Network Adapt
er
Physical Address. . . . . . . . . : 00-16-B6-4E-99-55
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.34.249
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :


C:\>ping 192.168.2.1


Pinging 192.168.2.1 with 32 bytes of data:


Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.


Ping statistics for 192.168.2.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms


C:\>







The IP address is way off. What's a good question to pose to the
landlord/network admin, please?

Is there anything which I can do on my end, short of dragging my
desktop around? The landlord
doesn't want to muck with cables, so I can't physically wire geidiprime
to the router.



thanks,

Thufir
 
(e-mail address removed) wrote in @i40g2000cwc.googlegroups.com:
The router: SMC7004VWBR-CA

My connection is 802.11b/g, as is my neighbors. The landlord has a
wired connection. My old computer worked fine with this particular
router for a long time, but the new computer isn't "playing well" for
unknown reasons.
Click to expand...
[snip]

IP addresses 169.254.x.x indicates that DHCP was unsuccessful in
negotiating an IP lease -- probably due to failure to connect.

Assuming that your neighbors still can connect to this router, then it
seems likely that there is a setting on your wireless device that is
incompatable. Go to the Device manager
(right-click "My Computer"->Manage->Device Manager)
Find your device under Network adapters and double-click it. There
should be an advanced tab that may offer a setting that will get you up
and running again.

You may also want to go to the website of your wireless adapter
manufacturer and see if there are any updated drivers available for
download for your wireless device.

You might also go to the SMC website and download the manual for the
router and see if there are any router settings that would exclude your
connection.

HTH,
John
 
John Wunderlich wrote:
[...]
IP addresses 169.254.x.x indicates that DHCP was unsuccessful in
negotiating an IP lease -- probably due to failure to connect.
Click to expand...
[...]

After resetting the router all's well. I'm curious, though, as to what
wasn't working properly. There was a computer, "A", with a wired
connection which worked fine, and "C", which was wireless, which worked
fine, and "arrakis", which worked fine.

The power supply on arrakis died, so I switched to geidiprime, and got
this connection error.

?


here's an ipconfig using an Asus WL-330g wireless wi-fi 802.11g NIC
connected to the ethernet RJ45 port. It looks like a wired connection,
but isn't:

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\>ipconfig/all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : geidiprime
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter 3com:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100
PCI TX NIC (3C905B-TX)
Physical Address. . . . . . . . . : 00-10-4B-70-F1-87
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.179
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
Lease Obtained. . . . . . . . . . : Saturday, June 17, 2006
11:14:44 PM
Lease Expires . . . . . . . . . . : Saturday, June 24, 2006
11:14:44 PM

C:\>tracert 192.168.2.1

Tracing route to 192.168.2.1 over a maximum of 30 hops

1 <10 ms <10 ms <10 ms 192.168.2.1

Trace complete.

C:\>ping 192.168.2.1

Pinging 192.168.2.1 with 32 bytes of data:

Reply from 192.168.2.1: bytes=32 time<10ms TTL=255
Reply from 192.168.2.1: bytes=32 time<10ms TTL=255
Reply from 192.168.2.1: bytes=32 time<10ms TTL=255
Reply from 192.168.2.1: bytes=32 time<10ms TTL=255

Ping statistics for 192.168.2.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>ping www.google.com

Pinging www.l.google.com [66.102.7.99] with 32 bytes of data:

Reply from 66.102.7.99: bytes=32 time=200ms TTL=244
Reply from 66.102.7.99: bytes=32 time=150ms TTL=244
Reply from 66.102.7.99: bytes=32 time=230ms TTL=244
Reply from 66.102.7.99: bytes=32 time=111ms TTL=244

Ping statistics for 66.102.7.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 111ms, Maximum = 230ms, Average = 172ms

C:\>ping 66.102.7.99

Pinging 66.102.7.99 with 32 bytes of data:

Reply from 66.102.7.99: bytes=32 time=440ms TTL=244
Reply from 66.102.7.99: bytes=32 time=331ms TTL=244
Reply from 66.102.7.99: bytes=32 time=290ms TTL=244
Reply from 66.102.7.99: bytes=32 time=170ms TTL=244

Ping statistics for 66.102.7.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 170ms, Maximum = 440ms, Average = 307ms

C:\>




thanks,

Thufir
 
(e-mail address removed) wrote in
[...]
IP addresses 169.254.x.x indicates that DHCP was unsuccessful in
negotiating an IP lease -- probably due to failure to connect.
Click to expand...
[...]

After resetting the router all's well. I'm curious, though, as to
what wasn't working properly. There was a computer, "A", with a
wired connection which worked fine, and "C", which was wireless,
which worked fine, and "arrakis", which worked fine.

The power supply on arrakis died, so I switched to geidiprime, and
got this connection error.
Click to expand...

It is impossible to guess the problem's source unless you look at the
router's configuration. It is possible that it is set to only assign 3
or 4 DHCP addresses. The DHCP Lease time is one week, so if a client
died it could take up to one week for the router to release its
reservation of that IP address and allow another computer to use it --
without resetting the router, of course.

Glad it's working.
-- John
 
Back
Top