Can't Connect to the Net

I have bought a new PC and I installed XP Pro SP2 on it.

I then bought a Wifi Card and installed that into the computer.

After installation, it managed to connect to the net once but since then, it can't connect to the net.

I need to find out what's stopping it from connecting to the net and fix it.

The PC connects wirelessly to the Router for Broadband connection.

I have tried putting in an IP address in the TCP/IP Properties and I have also tried to let it go automatically.

Either way, it's just not connecting to the net through IE or FF.

Can someone help?

JH

 

Can you PING the router? Find the router's IP address, then go to Start> Run> Command> PING XXX.XXX.XXX.XXX (using the router's IP address). If the response is normal, no packets will be lost.

 

yes, when I ping 192.168.1.1, it pings ok with 4 replies.

What else can I do?

JH

 

Windows IP Configuration



Host Name . . . . . . . . . . . . : cadspc

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No



Ethernet adapter Wireless Network Connection:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : TP-LINK 11b/g Wireless Adapter

Physical Address. . . . . . . . . : 00-21-27-DE-25-99

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.1.12

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.1

DNS Servers . . . . . . . . . . . : 192.168.1.1

4.2.2.2



Tunnel adapter Teredo Tunneling Pseudo-Interface:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : 00-00-FB-FB-C1-C7-93-DE

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 3ffe:831f:d5c7:a2d6:0:fbfb:c1c7:93de

IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%4

Default Gateway . . . . . . . . . : ::

NetBIOS over Tcpip. . . . . . . . : Disabled



Tunnel adapter Automatic Tunneling Pseudo-Interface:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : C0-A8-01-0C

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : fe80::5efe:192.168.1.12%2

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

NetBIOS over Tcpip. . . . . . . . : Disabled


Any clues?

When I tried pinging yahoo.com, it said that it was trying to connect to 1.0.0.0 and this is the same for any website.
Maybe there's a clue there!

Appreciate the help,

JH

 

From info everyone had you give it’s time to check if router is getting a DNS address from your ISP.

Enter this one either in the router or as second alternate one in computer: 208.67.222.222 or 208.67.220.220. That’s OpenDNS (you can google them) and OK to use.

If it works find out what your ISP’s DNS server addresses are. You can keep the OpenDNS address as an alternate.

 

I got the 4.2.2.2 address from another techie online.

I have now tried inputting 208.67.222.222 and 208.67.220.220 into the secondary alternate setting instead of 4.2.2.2. It still doesn't work.

I looked up my ISP website and in their Q&A, it says:

-------
Can I use Demon as my secondary DNS?

No.
-------

Under all these situations, it still does not connect to the net.

Any ideas or more suggestions?

JH

 

Yes – to finish testing if DNS is an issue.

At a cmd prompt type: tracert www.yahoo.com <enter>

Should resolve the name to IP address of 209.131.36.158
and after a few hops get there.

If name not resolved to IP address do a: ping 209.131.36.158

If 1st didn't work but ping did there's a DNS problem.

 

I did a tracert as you suggested and this is what I got:
I just edited the IP digits at the end.


Tracing route to www.yahoo.com [1.0.0.0]

over a maximum of 30 hops:



1 1 ms 1 ms 1 ms mygateway.G604T [192.168.1.1]

2 38 ms 22 ms 22 ms anchor-hg-3-lo100.router.demon.net [194.159.161.AB]

3 36 ms 23 ms 22 ms anchor-access-4-s156.router.demon.net [194.159.161.CDE]

4 anchor-inside-4-g6-0-4.router.demon.net [194.159.161.FG] reports: Destination host unreachable.

Trace complete.

However, the ping did work and I received a reply 4 times.

What does that mean and how should I proceed?

JH

 

That tracert has got outside your network. That shows the problem is not with your system (your router has done its job by passing on the packets to the ISP's router, and your DNS system is working or it wouldn't have resolved the yahoo address).

Send the tracert result to your ISP (or ring them and read it out to them). It looks like they have a problem on one of their routers.

Is the ISP demon internet? If so they have a good reputation and I'd be surprised if they didn't take a tracert output like that and deal with it promptly.

 

Actually I disagree.
Problem is DNS either with ISP or in network.
Would be surprised if it's ISP's DNS server.

That 1st tracert line: Tracing route to www.yahoo.com [1.0.0.0]
should have read: Tracing route to www.yahoo.com [209.131.36.158]
or something similar depending on how many IP addresses yahoo has.

As you mentioned for some reason you're stuck on that 1.0.0.0 for everyone.
Good observation. Works when you're not.

Try this:
On computer put the DNS addresses I gave you as the ONLY DNS addresses delete your router 192.168.1.1 but keep it as the gateway - need that.

Make sure you're doing it for the wireless connection and not a wired one.
did that once - no many how changes I made nothing happened -- LOL

If that works then we can take a look at router menu. Linksys?



ps
while in network properties do this under Advanced -WINS tab - uncheck enable LMHOSTS lookup. check default for NetBios setting.

 

Good point - well presented