Question : IP config with Qwest DSL, Cisco 678, Sonicwall SOHO3 and static IPs

Sonicwall SOHO3 set up as my DHCP server issuing private IPs to my local LAN (Win 2k machines)

connected to a Cisco 678 DSL Router connected to Qwest DSL

When my Cisco is configured to pull is IP info via DHCP from Qwest, everything works fine, Sonicwall pulls its WAN IP info from the Cisco, the Cisco gets a WAN IP 63.230.203.254 and and IP of 10.0.0.1, the Sonicwall receives an IP of 10.0.0.2 and a gateway of 10.0.0.1 and subnets of 255.255.255.0

Like I said, the above works perfectly, the LAN computers get IPs in the 192.168.168.x range, they use 192.168.168.1 (sonicwall internal IP) as they're gateway, they can surf the net, access email, the sonicwall protects us, we're happy, yada yada....

Now.... I leased a block of static IPs from Qwest, got assigned 209.180.147.128 thru 209.180.147.135.  The label .128 as Reserved Network, .134 as Reserved Gateway, .135 as Reserved Broadcast, and the other 5 as user assignable.

Here's what I do to configure the Cisco 678
set nat disable
set dhcp server disable
set ppp wan0-0 ipcp 0.0.0.0
set ppp wan0-0 dns 0.0.0.0
set ppp wan0-0 login ktpc1
set ppp wan0-0 password xxxxxxxxxxxxxx
set int eth0 address 209.180.147.134
set int eth0 netmask 255.255.255.248
set int wan0-0 disable
set int wan0-0 close
set int wan0-0 vpi 0
set int wan0-0 vci 32
set int wan0-0 enable

write
reboot

I configure the Sonicwall to work in NAT enabled mode
I keep the LAN IP at 192.168.168.1 the mask as 255.255.255.0
I set the WAN Gateway address as 209.180.147.134
I set the sonicwall WAN (NAT Public address) as 209.180.147.129 (the first of my five user assignable)
I set the sonicwall WAN subnet as 255.255.255.248
I set the DNS servers to 206.80.192.1 and 204.147.80.5 (per Qwest)


I cannot surf the web, check email, nothing from my workstations.  

Here's what I can do

From the Cisco - I can tracert all the way to the DNS servers (and presumably beyond)

From the sonicwall I can tracert as far as 63.230.203.254 (the WAN IP of the Cisco)
From the workstations I can tracert as far as 63.230.203.254 (the WAN IP of the Cisco)

Of course Qwest says its not their problem, sonicwall says its qwest's problem, blah blah.

I think the problem lies in the Cisco, I don't think it knows to route traffic from the LAN to the WAN, how do I check this?

Qwest did say it takes 24 hours for the IPs to become "routable".  That was 30 hours ago.  Is it possible that I just need to wait it out longer, or I am configuring something wrong?

Answer : IP config with Qwest DSL, Cisco 678, Sonicwall SOHO3 and static IPs

sure. Sometimes I would order a static ip block, set everything up on the cisco 678(i have done this 21 times for my job) and got nowhere fast. Sometimes the flunky at Qwest enters your info wrong, and your addresses dont stick.

If possible have a buddy try to do a tracert from his internet connection. Then do a tracert to him. Is the last live hop the same on each end? if so, it is a routing problem; you need to delete the range, and readd them from qwest.net.

I would also not discount the importance of erasing the nvram.

One last thing, make sure you can travel outside the qwenron network, i.e. try traceroute to yahoo.com or redhat.com. Sometimes I have been able to trace to the dns servers, but not to the real internet. My packets would fly around qwestland until the ttl exceeded.

If you can never connect it is a line problem.
If you can connect with DHCP, but not Static, it is probably Qwest screwing up your day.

On the bright side, once it is set up, it will run forever with no major problems. Ours have neeb very reliable. We have 21 cities using qwest dsl lines and cisco routers for VPN to our HQ in Phoenix.