Can't Connect to Verizon Avenue using Belkin Router

Please sell me on Expert's Exchange.  This was posted for a week elsewhere with not one response.

I use the Verizon Avenue service and am having trouble connecting to the service using my Belkin Wireless Router. I can connect easily by plugging the ethernet connection from the modem to my laptop, but when using the router it is a different story.

Hardware:
Modem: Alvarion - Model Number: 0334B5555 - it also says PS1073 on it. I believe it is a DSL modem.

Router: Belkin Wireless N Router
Firmware Version 1.00.02 (Jul 31 2008 22:32:30)
Boot Version V0.13
Hardware F5D8236-4v1(01)

The first thing I did was clone my Laptop's Ethernet MAC Address to the Router to ensure there were no MAC filtering issues. I don't suspect a technical issue with the router as it was previously used and worked perfectly connected via a cable modem, which I dearly miss.

I have tried using a Dynamic IP, a Static IP (because the IP appears to not be changing), and PPPOE as connection methods in the router configuration for connection type. It seems to get closest when using Dynamic, because when configured that way I have gotten to the point where the router shows a blue light for the modem (indicating a proper connection) as opposed to the flashing amber light it shows for the other two modes, but I still do not get to the point of being connected to the Internet. As soon as I plug the network cable straight back into my laptop it works fine.

This is a paste of IPCONFIG/ALL at the command prompt. If I am blocking out anything that is necessary please let me know:

ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . :
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : vzavenue.net

Wireless LAN adapter Wireless Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : Belkin
Description . . . . . . . . . . . : Intel(R) WiFi Link 5100 AGN
Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : vzavenue.net
Description . . . . . . . . . . . : Marvell Yukon 88E8071 PCI-E Gigabit Ether
net Controller
Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : xxxx::xxxx:xxxx:xxxx:xxxx%10(Preferred)
IPv4 Address. . . . . . . . . . . : 66.xx.xx.xx(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Saturday, April 10, 2010 9:44:36 AM
Lease Expires . . . . . . . . . . : Monday, April 12, 2010 9:44:36 AM
Default Gateway . . . . . . . . . : 66.xx.xx.xx
DHCP Server . . . . . . . . . . . : 66.xx.xx.xx
DHCPv6 IAID . . . . . . . . . . . : xxxxxxxxx
DHCPv6 Client DUID. . . . . . . . : xx-xx-xx-xx-xx-xx-xx-xx-xx-xx-xx-xx-xx-xx

DNS Servers . . . . . . . . . . . : 66.171.48.85
66.171.40.85
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : vzavenue.net
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : xxxx:x:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx(Pref
erred)
Link-local IPv6 Address . . . . . : xxxx::xxxx:xxxx:xxxx:xxxx%12(Preferred)
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 12:

Connection-specific DNS Suffix . : vzavenue.net
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : xxxx:xxxx:xxxx::xxxx:xxxx(Preferred)
Default Gateway . . . . . . . . . : xxxx:xxxx:xxxx::xxxx:xxxx
DNS Servers . . . . . . . . . . . : 66.171.48.85
66.171.40.85
NetBIOS over Tcpip. . . . . . . . : Disabled
malice132Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Brain2000Commented:
I'll take a shot at it.

First, power cycle the Verizon unit.  That usually allows it to accept a different MAC address.  Though you cloned it already, but just in case the Belkin has a bug and isn't using the cloned address...

Two, make sure the Belkin is set up for 192.168.1.1 with subnet 255.255.255.0 internally, and that DHCP is on (i.e. 192.168.1.x).

Three, hook up your laptop, via Ethernet (not wireless or USB) to the Belkin, and verify that you receive a 192.168.1.x address, using "ipconfig /all".

Four, make sure you can browse to 192.168.1.1 and see the Belkin configuration screens.  If you can't see the Belkin, you're not going to see past it to the internet either,

Five, set the Belkin to Dynamic IP address.  This will allow the Belkin to get a public IP address/gateway/DNS servers from Verizon's DHCP servers.

At this point, the Belkin should have a public IP address on the outside and 192.168.2.1 on the inside.  You should be able to communicate with it on the inside.  And finally, it should be happily NAT'ing your connections to the internet.  Now you can get the wireless part working (use WPA-PSK, not WEP) and you're on your way.
0
Brain2000Commented:
If your laptop keeps getting a 169.x.x.x number, it isn't getting DHCP from the Belkin.  You can run "ipconfig /release" and "ipconfig /renew" to drop and refresh DHCP on the computer.
0
malice132Author Commented:
I changed the internal IP from 192.168.2.1 to 192.168.1.1 as well as the sub-IP's.  I can't imagine why that would have an effect but thought I would give it a shot.

I rebooted the verizon modem, but I am certain they do MAC filtering because they make you register the MAC on the website in their utilities.  They support two MAC addresses so I had already added the router's default MAC address, just in case.

DHCP is on and my laptop is assigned 192.168.1.2 (previously 192.168.2.2 before I changed the router's internal IP).  I have been connecting directly with an ethernet cable and will continue to do so until I can get on the internet through that.  I'm not worried about wireless.

The router is set to dynamic.

I am still not getting a connection, although a new development has popped up.  Now when I connect the modem to the router, I am unable to get to the router's configuration screen.  The modem light on the router is blinking amber (where previously it was solid blue when connecting dynamically) and I can't get into the configuration screen until I disconnect the modem and reboot the router.  I have verified that the router is using the latest firmware.  I'll continue messing with it and see I can get something new to happen.
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Brain2000Commented:
Just to verify, your laptop got 192.168.1.2 automatically from the router?

Can you ping 192.168.1.1?

I'm assuming that you configured it with a USB cable?  If that is the case, did you unplug the USB when done?  Some routers don't allow both USB and ethernet simultaneously.

You can't get into the configuration screen until you disconnect the modem and reboot the router... can you explain a little more here.  This sounds very strange.  Whether or not the modem is connected shouldn't have any affect on the router being able to be configured.

I just had a far fetched thought.  What if the router is getting the MAC address between the WAN and LAN mixed up.  If you can't ping the router, try changing the MAC address back to the default, reset everything, and try and ping it again.  I've never heard of this happening, but we have an odd situation here.
0
Brain2000Commented:
You could also have a bad ethernet cable.  Let's try switching those out while we're testing.  Just so we can rule that out.
0
Brain2000Commented:
Let me verify one more thing to get this out of the way.  You are plugging the modem into the yellow slot, right?
0
Brain2000Commented:
One more thing.  In the router configuration, click on "Wireless" on the left menu, and make sure "Use As Access Point" is "Disabled".  You don't want to use it as just an access point or it will disable functionality that we need here.
0
malice132Author Commented:
Alright, so let's see where we are.  I just had an issue even getting back on the Internet with my laptop directly connected to their modem.  I was able to get through to their technical support who had me go to their web page, delete my computer from the profile and re-add it.  They allow two MAC addresses as computer profiles, but mine wasn't working for some reason so I had to delete it then re-add it.  While I was on the phone with them I asked about router configuration and she said that you just needed to set it to dynamic and turn on DHCP, but I got the feeling they don't really support configuring a router.

When I am configuring the router, I am connecting directly to it via an ethernet cable and am not connected to the internet.  I then connect another ethernet cable between the modem and the router to try to connect them.  I am still having the issue that I can't get to the router's configuration screen when it is connected to the modem.

I backed up the router's configuration and restored it to factory default.  Conveniently, the default firmware is the latest version.  I then disabled wireless so that it wouldn't even be an issue.  I verified that the access point option is disabled.

After the ordeal getting back on the Internet, I got an idea.  What if I left the router set to its default MAC address and attempted to connect to the Internet?  Hoping that this would bring me to the configuration screen on their website where I could then add its MAC address, I gave it a try, but no dice.  I then tried manually adding the router's MAC address to the site and connecting, but it still didn't work.

And yes, I am plugging the modem into the yellow modem slot on the back of the router.  If it were something that simple I think I would slap myself.

I'll do some more test runs.  Oh, and I have verified that the ethernet cables are working fine, as well.  Thanks for the help, though.
0
malice132Author Commented:
The only other thing I thought of was if for some reason my router wasn't passing the configuration web page through.  By this I mean this ISP has you go to that page where you add your MAC address and then you are free to roam the Internet, but you aren't technically connected until after this step is done.  If for some reason the router isn't passing this through to me so I can configure it then I'm not getting to the next part where I am connected to the Internet.  Other than that I feel like I'm at a loss.  I don't suspect the router because I've used it fine before.  I know the modem works because I'm using it right now, and I know the cables are good.
0
malice132Author Commented:
For my last attempt for the night, I got the router to actually show blue for the modem (indicating connected) and blue for the internet (indicating connected).  I nearly jumped out of my chair.  Unfortunately, I wasn't actually able to get to anything on the Internet, and again I was not able to get into the router's configuration screen once the modem was connected.  I did do an IPCONFIG /all, and it just showed the belkin (router), a locally generated IP for the ethernet connection, and the router's IP address as the default gateway.  And when I try to ping the router the request times out, although when I do this without it connected to the modem it returns pings just fine.  And then as a test I started pinging the router and then connected the ethernet cable from the modem to it while I was pinging it and this is what I got:

Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.2: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

I'm more puzzled than when I started.
0
Brain2000Commented:
If you unplug the modem after it stops pinging, does it start pinging again?  If you wiggle the ethernet cable does it start pinging again?

I guess I'm trying to find out, is the modem causing something in the router to stop responding, is a cable getting bumped, or is the router crashing?

I'm starting to lean toward you might have a bum router.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
malice132Author Commented:
Here is a copy of me pinging the router with comments added:

ping/t 192.168.2.1
//started pinging with laptop connected to router, modem not connected
Pinging 192.168.2.1 with 32 bytes of data:
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Request timed out.//Here I connected the modem to the router
Request timed out.
Request timed out.//During this time I was wiggling the four ethernet connections
Request timed out.
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64//unplugged the modem from the router
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Request timed out.//plugged the modem back in
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.//gave the router a long time with the modem connected
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.//around here is when I unplugged the modem
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.//the router is still not responding with modem unplugged
Reply from 192.168.2.2: Destination host unreachable.
Request timed out.//started getting these.  The modem is not plugged in for the rest of the time
Request timed out.
Reply from 192.168.2.2: Destination host unreachable.
Request timed out.
Reply from 192.168.2.2: Destination host unreachable.
Request timed out.
Request timed out.
Reply from 192.168.2.2: Destination host unreachable.
Request timed out.
Request timed out.
Reply from 192.168.2.2: Destination host unreachable.
Reply from 192.168.2.2: Destination host unreachable.
Request timed out.//unplugged the router from the laptop
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.//plugged the router back in
Reply from 192.168.2.2: Destination host unreachable.
Reply from 192.168.2.2: Destination host unreachable.
Reply from 192.168.2.2: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.2.2: Destination host unreachable.
Reply from 192.168.2.2: Destination host unreachable.
Request timed out./restarted the router
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=736ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=66ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64

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

At this point, I think I may have to agree with your assessment of "bum router".  It is just surprising because it worked fine before I moved, but everything does have a certain working product life.  I think I'll go pick up a new router today and give it a shot.  Worst case it doesn't work.
0
Brain2000Commented:
True that.  The only other test I would try before exchanging it for a new one is pinging with a different computer.  I don't think you will see any different results, but that will almost surely confirm it.

Here's what I don't want to see happen.  You exchange it for a new one, and the new one does the same thing.....
0
malice132Author Commented:
Well, I guess I will have to say that your guess was correct.  I just went and bought a new router (Netgear Wireless N-300) and I am posting this using the router.  I am so frustrated, and elated, that it is hard to express.  This thing was nice and easy to setup, as well.  I have actually never had a router that was so easy to configure.

But in any case this thing is closed.  For some reason the Belkin didn't want to talk to the DSL modem, but the Netgear was on in minutes.  It took me right to the registration page where I added it's MAC address and now I'm back into wireless world again.  Thanks for the help, and I'll award you the points for "bum router".
0
malice132Author Commented:
Stuck through with it to the end.
0
Brain2000Commented:
Cool, glad it worked out in the end.  They're supposed to be easy to set up... well, most of the time.  Good luck!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Telecommunications

From novice to tech pro — start learning today.