Tech Support Forum banner

SBC DSL Initial Connectivity Problems

3818 Views 4 Replies 4 Participants Last post by  Pseudocyber
Hey all . . .

I'm running Windows 200 Professional on a laptop and recently signed up with SBC for DSL. I have a Speedstream 5360 DSL modem.

During the install process, I was able to log in using EnterNet 3000, but I am unable to establish a TCP/IP connection. Pinging www.yahoo.com brings back "destination host unreachable" and all attemps to access the web return "Cannot find server".

I worked with SBC support, but they have been unable to resolve the problem. They mentioned something about uninstalling all other network services, but I use this machine on a LAN at work, so I can't do that.

Any ideas?
Status
Not open for further replies.
1 - 5 of 5 Posts
Welcome to the board, :D

Are you being assigned a IP via DHCP or is it static?

Also check via ipconfig to make sure that your IP provider and other Network connections are not both fighting for the same subnet, this is a common problem.

and last Do you have any kind of firewall installed?
More detail

Thanks for the welcome, and sorry about my double-post. :uhoh:

>> Are you being assigned a IP via DHCP or is it static?

I went through the steps with the SBC rep to configure Enternet 300 to use DHCP. Also, my work network uses DHCP as well.

>> Also check via ipconfig to make sure that your IP provider and
>> other Network connections are not both fighting for the same
>> subnet, this is a common problem.

I'll try this tonight when I get home. If they are, how would I resolve?

>> and last Do you have any kind of firewall installed?

I use BlackICE, but I disable it when I'm at home.


__________________
See less See more
Make sure you have an IP address at *all*.

Start > Run

cmd.exe

Code:
ipconfig
Paste what you have in there. Your DHCP server could be naughty, or you might just be failing to snag an IP at all.

My own personal curiosity.
See less See more
If after running ipconfig and you have an address here are the next steps.

0.) Turn off firewall while troubleshooting
1.) Ping 127.1.0.1 - this will ensure your TCP/IP stack is functioning properly.
2.) Using Ipconfig /all make a note of your IP address, your default gateway address, and the DNS server addresses.
3.) Ping your own IP address - this will verify your NIC is working.
4.) If your router has an address, Ping it.
5.) Ping your default gateway. This will verify your connectivity to your provider.
6.) For the halibut, ping your DNS server addresses.

If all of the above works, you are on the network and working properly, so far.

Since you're using Windows 200(0) (;)) do this:
At a command prompt type --> nslookup

This will fireup a utility that connects to your DNS server. You'll be at a > prompt and they'll probably have it locked down so you won't be able to do much. You can type a ? to see a list of commands you can run.

Type in this >www.cisco.com

You should get back this:
> www.cisco.com
Server: removed.to.protect.the.guilty.com
Address: x.x.x.x

Non-authoritative answer:
Name: www.cisco.com
Address: 198.133.219.25

This was a command telling your DNS server to lookup the name for Cisco and give you the address.

If this doesn't work, contact your provider and tell them you are having some DNS issues and tell them what you did.

If it does work - get back to us. And we'll go from there! ;)
See less See more
1 - 5 of 5 Posts
Status
Not open for further replies.
Top