SWB DSL Access Problems

[mired]

Have a small workgroup/LAN. Used to be 2 PCs running win2kpro connected to Netgear 5-port hub with 1 SWB DSL line connection to hub and from there to DSL modem shared with another LAN in a different office. IP addresses are assigned automatically - DHCP. Occasionally had problems with DSL access, but usually OK. Just added a 3rd PC to our LAN running winME.

Everything was working great for a couple of days. Then today suddenly there is no Internet/e-mail access from our LAN - in IE we get the "This page cannot be displayed" and DNS error message and Outlook returns "servers not found - blah, blah" error messages. Meanwhile, the DSL connection for the LAN running in the office next to us that shares our DSL modem is working fine. ANY IDEAS??? PLEASE HELP!!!

Have checked all obvious stuff like network cables, etc., and spoke with SWB. I don't know, should we be assigning IP/DNS addresses to correct the problem?

 

[boxplan]

There are three or four earlier threads that discuss SWB and DSL connections in general. Yu can find them by searching for SW Bell I am watching these because I can't connect to my SWB DSL at all through my SMC Barricade router. I have followed the suggestions but I’m still missing something. I'm trying to connect using DHCP also. What DNS addresses are you using?

 

[mired]

Thanks - I read some of the SWB messages last night (after posting) and decided it might be a DNS address problem. Obtained SWB DNS addresses 151.164.1.8 & 151.164.1.7, plugged them in, and everything is working great. Hope maybe this works for you. Good luck.

 

[boxplan]

I've tried 151.164.1.8 & 151.164.1 and still can't connect. At least I know that the DNS addresses aren't the problem.

Maybe someone else will have an idea. I have not found much information on the SMC Barricade router. I'll keep looking.

Thanks for the info.

 

[boxplan]

Here's something that I found: {Thanks to the !unknown! originator!

In general you should allow the DNS server to be obtained when you get an IP. However you may find one of the other DNS servers provide better speed for you. Here is the last known list of new DNS servers:
Abilene ........... dns1.ablntx.swbell.net [151.164.166.201]
Amarillo .......... Same as Dallas
Austin ............ dns1.austtx.swbell.net [151.164.20.201]
Beaumont .......... dns1.bumttx.swbell.net [151.164.160.201]
Corpus Christi .... dns1.crchtx.swbell.net [151.164.79.201]
Dallas (Richardson) dns1-rcs.rcsntx.swbell.net [151.164.1.8]
El Paso ........... Same as Houston
Fayetteville ...... dns1.fyvlar.swbell.net [151.164.169.201]
Fort Worth ........ Same as DallasHarlingen ......... Same as Houston
Houston...........dns1-hst.hstntx.swbell.net[151.164.11.201]
Kansas City ....... dns1-kcy.kscymo.swbell.net [151.164.8.201]
Little Rock ....... dns1-lr.ltrkar.swbell.net[151.164.64.201]
Longview .......... Same as Houston
Lubbock ........... Same as Dallas
Midland ........... dns1.mdldtx.swbell.net [151.164.34.201]
Oklahoma City ..... dns1.okcyok.swbell.net [151.164.23.201]
San Antonio ....... dns1.snantx.swbell.net [151.164.17.201]
Springfield ....... same as Kansas City
St Louis .......... dns1-stl.stlsmo.swbell.net [151.164.14.201]
Topeka ............ dns1.tpkaks.swbell.net [151.164.172.201]
Tulsa ............. dns1-tulsok.tulsok.swbell.net
[151.164.67.201]
Waco .............. Same as Dallas