I'll keep it short as I don't know a lot about these types of things. Basically, I can't ping any website. I've opened up msdos and typed in ping www.computing.net and it comes back "Request timed out" 4 times. I've turned off my firewall and tried it but that didn't help. I've tried running Nslookup and get the following message: *** Can't find server name for address 192.168.1.1: Non-existent domain *** Default servers are not available Default Server: UnKnown Address: 192.168.1.1 What could the problem be? Thanks.

The problem could be that you are not connected to an ISP, or that the Domain Name Server is/was down. How about some more info: Dial-up or DSL or Cable? Using a router? When you do an IPCONFIG /ALL (in a command or msdos window), what do you get for IP, mask, gateway, DNS? From the little info you gave, it sounds like you are connected to a router; if so, is it connected to the internet? Terry

DSL connection with a router. I can connect to the internet ok. I am using the connection at the moment. IPCONFIG: Host Name . . . . . . . . . . . . : DGND331J Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection 6: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : ZyXEL USB ADSL Modem #3 Physical Address. . . . . . . . . : 00-A0-C5-9A-FF-F3 Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.1.33 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DHCP Server . . . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 192.168.1.1 Primary WINS Server . . . . . . . : 128.0.4.0 Secondary WINS Server . . . . . . : 39.123.0.0 Lease Obtained. . . . . . . . . . : 20 May 2005 16:57:14 Lease Expires . . . . . . . . . . : 23 May 2005 16:57:14

Are you saying that the problem has gone away, or that you have good internet connection with your browser but cannot successfully ping? If the latter, I'm really stumped, but try to isolate with the following series to see where the first failure occurs: ping 127.0.0.1 (loopback) ping 192.168.1.1 ping 69.93.141.100 (www.computing.net) ping www.computing.net Terry

>Are you saying that the problem has gone >away, or that you have good internet >connection with your browser but cannot >successfully ping? Yes the latter. >If the latter, I'm really stumped, but try to >isolate with the following series to see >where the first failure occurs: >ping 127.0.0.1 (loopback) >ping 192.168.1.1 >ping 69.93.141.100 (www.computing.net) >ping www.computing.net The first 2 work, the other to don't.

It is most likely some kind of firewall problem. It may not even be your firewall, it could be the ISP firewall. I have this same issue from my home and I have no firewall. It never has caused any other problems though (have always been able to surf with no problems).

Thanks, Mike. I hadn't heard before about some ISPs being so (over-) protective. Sorry, gearoid; I shoulda waited for Mike's posting. You could check with your ISP to confirm that this really is their policy. Terry