Now to the weird problem that I am experiencing.I have a P4 1.7 GHZ with 256 MB Ram and a 40gb hard disk.My pc has a double booting option.One is Win Me(I know,I know) and the other is Win XP Pro.
Now surprise surprise,my Win ME is giving me some strange errors.Till yesterday the explorer in ME was crashing for no reason at all leaving me no option but to reboot.So I decided to re-install the whole thing.Only after the re-install did the current problem start.I use broadband to surf and I connect via a LAN card.I installed the drivers for the lan card and no conflict is being reported. Now here is the strange part. I cannot access the net at all inspite of trying two different browsers(Opera and IE).All it says is “Cannot Find Server”.Even my Yahoo Messenger and MSN Msgr dont connect anymore.But I use a P2P software and it is connecting normally and even downloads stuff.(Real apologies to the mods if I am violating board rules by mentioning the P2P part,but I feel it is an important info.Feel free to take the neccesary action if this is in violation).
I spoke to the tele support people at my ISP and was told something to the context of “Your TCP/IP protocol is corrupted”.I was just wondering if if there is any way to repair the said problem or will I have to do a re-install again?I am pretty adept with pc’s and I have checked all the details in the Settings>Control Panel>Network Connections(which seem to be alright).Any help will be aprrecieted.
Obviously, you are not only routing to some hosts (P2P working), buy you are also transmitting and receiving. That kind of throws cold water on the TCP/IP being corrupted (Transmission Control Protocal and Internet Protocol).
What it sounds like is the P2P software uses IP addresses, but normal surfing uses DNS. Using DNS, a convenient name is translated, or resolved, to an IP address. It sounds like your requests are not being resolved to IP addresses and routed to destinations.
But they are when using XP.
Don’t know how to troubleshoot that in windows.
For other operating systems, I would ping my ISP by DNS name. For example, I just pinged my news server to see if it would work. It did. To do that, my computer had to have some way to translate news.central.cox.net to an IP address. There were a few responses I may have gotten:
A reply.
Network unreachable. This means the name was resolved to an IP address but for some reason the network wasn’t reachable. Routing/physical cable problem; not DNS.
Unknown host. Can’t resolve name to address. DNS problem.
Absolutely nothing. Interface on local computer not even getting to router/gateway/next network entity.
But TCP/IP is not corrupted. You are transmitting and receiving using Internet addresses. Call your ISP back and ask them not to blow smoke up your butt.
Corrupted TCP/IP. What’s next? They tell you the problem is between the chair and the keyboard? Ask you to empty the bit bucket? Spray some frequency cleaner?
So, it is resolving the name to an IP address, but you are not getting a reply to your ping.
This doesn’t mean your network isn’t working. One reason you can get to the P2P network but not receive a ping reply might be that the firewall for your ISP is blocking pings.
You didn’t get “network unreachable” and it wasn’t exactly silent.
Call your ISP. Tell them what you have found. Ask them to walk you through a test to make sure you can reach them.