Windows Forum

Ask something
Discussion Locked

windows 2000 unable to browse internet

0 helpful
7 replies

by mishratron

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I made a w2k server for home testing while self studing for MCSE.
I have DSL Service
For a good period of time I was able to connect to swbell and browse the internet.
connectivity has since stopped.
I am able to send out pings and tracerts I amable to get DNS
I can ping fqdn's
I can not connect to any webdevice via dns or direct IP
I do not remember changing any configuration settings
Any browser I try tells me I am offline
I have had the modem tested.
there are no device conflictsI have tested the connection with a known good computer and it is fine.
there are no restriction
I tried taking the computer over to a friend's house to test his known good connection and I get the same thing
ping
tracert
ping w/&w/o dns
Some one please help I am running out of ideas. I know it is a configuration issue on my end but where?

7 replies

by gazza-sa

Try uninstalling dial up networking from the add/remove programs, windows setup.
restart and reinstall DUN.

hope it helps

by mishratron

The line technician tried that for me. SWBELL DSL is not part of DUN.
I believe DSL normally does not require a log in but the baby bells want it if you use dhcp
-chad
Thanks for the suggestion though!

by raffi_

The fact that you are getting DNS resolution and tracert leads me to believe that something is interfering with port 80 on your machine but I need more info.
Are you getting email?
Do you have a firewall installed?
Are you using NAT or ICS?
Areyou using any form of Proxy?

SF

by mishratron

Http, ftp, telnet all did not work, I have since reinstall the OS because SWBell suggested a registry problem so i now have a backup of a known good registry from now on.
Thanks for the help though.
Ps, no Firewall, nat ics or proxy, direct connection
one machine, wide open

by mphoffar

The only two places I can think of is either a) The security settings are jacked sky high or you have the IP security settings set and have most of your ports locked down.

A good way to test this would be to do a ping ftp.someserver.com:23 (or80 for that matter) and see if you get the same results that way.

Mark

by mishratron

that is the best idea so far, but alais I did check my security settings and pinged off port.
I guesse SWBELL was right and there is really a registry setting that got f'd up
Thanks though !

This discussion is closed to new replies.