ATTBI madness, got any solutions?

[Demitre]

ATTBI says texas is 100% up. I'm in Texas my cable does not work. I powered cycled, set everything to disabled, and rebooted many times. I can release and renew to get ips and i can see 4 dns servers in my winipcfg. I tried to ping addresses that i know and always getting timed out. When i try to visit a website i get hanged on finding www.xxxxxx.com .

All of my cable lights are green.

This is my ipconfig output

Windows 98 IP Configuration

0 Ethernet adapter :

IP Address. . . . . . . . . : 12.255.174.49
Subnet Mask . . . . . . . . : 255.255.255.192
Default Gateway . . . . . . : 12.255.174.1

1 Ethernet adapter :

IP Address. . . . . . . . . : 209.245.253.120
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 209.245.253.120

The bottom one is my dialup modem
I pinged the gateway, no answer.
I can't access websites by using ip addresses.

 

[ScottMac]

Are you directly connected to your cable modem?
Did you power cycle the cable modem?
(if yes)
Verify in the NICconfiguration and "Internet Options" that there are no proxys defined, no domain name (home.com) OR change home.com to attbi.com.

The "255" in the second octet is a little unconventional, but should be OK (as long as it's not a typo from their side.

You may want to call their help desk to see if the address verifies with what they THINK you should have (try the Chat on the web site...it's not too painful).

Good Luck

Scott

 

[Garion]

If you have two default gateways, Windows will load balance between them. So, packet 1 goes out DG #1, Packet 2 goes out DG#2, Packet 3 goes out DG#3, etc. That's likely your problem.

Short answer is, you can really only have one NIC with a default gateway setting. Most TCP connections will.. Well.. survive 50% packet loss, but not well. UDP (such as DNS) will simply crash and burn, as it doesn't have any kind of retransmission and make-sure-the-packet-got-there algorythms.

The best bet is to setup some static routes to send traffic out your dial-up NIC. Use the Windows ROUTE ADD command (I think it's ROUTE ADD (subnet) MASK (mask) gateway. IE, "ROUTE ADD 172.20.0.0 MASK 255.255.0.0 10.52.22.1"

Windows doesn't remember these after a reboot, except in the NT family, where you can add a "/persistent:yes" (or something of the sort - route add |more should help). If you have a 9x/ME box, you need to setup a batch file which you can run on demand to setup the routes.

Best of luck!

- G