Can't Browse, but can in Safe Mode

Microsoft Windows xp professional w/sp2
May 27, 2010 at 09:24:06
Specs: Windows XP SP2
Oooook....

I've been through all of the other posts similar to this one on this any many other forums to no avail. Here's the situation:

I'm working on getting a laptop back online for someone (a ThinkPad). Right now, I've got it to the point where it will connect to the router and get assigned an IP, but I can't browse. When I boot into safe mode with networking, it will connect and browse just fine, using the same exact wireless profile. Normally, by this point, I would just reinstall XP and start fresh...unfortunately, the guy has *legacy* software he absolutely needs that he lost the disks for...ugh.

Just to save time on the responses, below are some bullet points of what I've tried/ what the scenario is:

-Windows XP Pro SP2
-Verizon DSL connection
-Same thing happens with the on board ethernet as well (direct into router wired)
-/ipconfig is completely normal; it finds the correct gateway, subnet and a unique IP for the network
-netbios is enabled
-no IP conflict
-can ping 127.0.0.1
-can ping the router, and other computers on the network; other computers can ping the thinkpad
-can NOT ping domain names
-tracert times out
-multiple other computers are able to browse just fine using the same settings
-tried IE8 (no proxy settings turned on, no addons), chrome, firefox, and safari
-ran the winsockxp fix
-disabled nearly everything except essential windows processes in msconfig
-windows firewall disabled
-no spybot or AV running/installed
-ran the long scan trendmicro housecall in safe mode and it found zilch.
-tried disabling security on the router and connecting that way, no dice
-tried telnetting to google.com via port 80 and pulling the header, once again, nothing

I'm at a loss at this point guys. Any ideas are appreciated.


See More: Cant Browse, but can in Safe Mode

Report •

#1
May 27, 2010 at 09:55:04
post an ipconfig /all for review
post the tracert results

Report •

#2
May 29, 2010 at 14:20:18
ipconfig /all:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\tattoo>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : unclebill
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domain_not_set.invalid

Ethernet adapter Wireless Network Connection 3:

Connection-specific DNS Suffix . : domain_not_set.invalid
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Networ
k Connection
Physical Address. . . . . . . . . : 00-13-02-B9-DC-52
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.64
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
71.242.0.12
Lease Obtained. . . . . . . . . . : Saturday, May 29, 2010 4:58:23 PM
Lease Expires . . . . . . . . . . : Sunday, May 30, 2010 4:58:23 PM

Ethernet adapter Local Area Connection 5:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Intel(R) PRO/1000 PL Network Connect
ion
Physical Address. . . . . . . . . : 00-16-41-A9-75-80

C:\Documents and Settings\tattoo>


tracert to google:


C:\Documents and Settings\tattoo>tracert www.google.com
Unable to resolve target system name www.google.com.

C:\Documents and Settings\tattoo>



Report •

#3
June 1, 2010 at 09:33:49
bump...any ideas?

Report •

Related Solutions

#4
June 1, 2010 at 14:17:01
None!

This is a most unusual case.

The only thing I can think of to try would be to uninstall both the wired and wireless interfaces in Device Manager (one at a time of course) and then reboot and let Windows "find" and install the devices.

If that doesn't do it, check to ensure you have the most up-to-date drivers.

If those don't fix it, try un/reinstalling the TCP/IP stack.


Report •

#5
June 1, 2010 at 14:24:49
Yeah, I should have put that in the original post, but I did delete both the wireless and the LAN from device manager and ran through the plug/play install via XP. That didn't work either. Drivers on both are up to date as well.

I'll try the TCP stack, but I'm not optimistic it will fix it.

Beyond anything, at this point, I really think there's some artifact of something in the registry somewhere that's blocking traffic past the router and/or DNS; The problem of course, is that I really have no idea where to begin to look. I had hoped the WinSockXPFix program would resolve that since it's supposed to reset a lot of the reg values for your network connectivity, but it didn't.

Any tips on where I can begin to look in the registry for problems?


Report •

#6
June 1, 2010 at 14:43:16
"DNS Suffix Search List. . . . . . : domain_not_set.invalid
Connection-specific DNS Suffix . : domain_not_set.invalid"

Why are you putting invalid dns search information? Don't do that.
If you can ping google.com there is nothing wrong with your tcp/ip stack

Provide a ipconfig /all when in safe mode for comparision.


Report •

#7
June 27, 2010 at 07:54:58
I tried to compile a list of everything that works on this in order
of likelihood of success:


1) virus / worm

unwise.exe, a phony Windows Antivirus program, and a
rootkit named tdss may have caused this problem.

run gmer, combofix, and malwarebytes to clean the computer
up.

2) Uuninstall Norton products with symantec removal tool (an
old symantec install may have left deviant code.) Norton may
have bits and pieces left on teh disk, use Norton Removal
Tool at
http://service1.symantec.com/Suppor...
5033108162039 to get EVERYTHING. McAfee, Trend Micro,
and Zone Alarm have all been causes of this proble,
seemingly due to a conflict with a windows update. Using
approrpaite uninstallers or teh Add/Remove Programs Control
Panel, you may want to uninstall your Anti-Malware entirely;
disabling alone may not be adequate.

3) Try to 'telnet google.com 80', 'ipconfig /renew' from the
command line, or right click the connection icon and select
"Repair".
If either of those give you a weird error, then it's probably
winsock corruption (Which only affects TCP, so i.e.: PING
works (IP only), but a TCP connection does not)
Run winsockfix or follow directions at:
http://support.microsoft.com/kb/811259

4) The Cisco VPN client has sabotaged browsing in one
case. If you use it, reinstalling it may help.

5) Replace hosts.ini with only 127.0.0.1 as an entry.

6) Ensure no proxies have been set if you don't have any. In
internet explorer, click tools > internet options. Then click
connections and LAN settings. Remove the checkbox for 'use
a proxy server'.

7) Revert to an older driver (or upgrade to another.) You may
need to run winsockfix again

8) Set BIOS to defaults to undo any overclocking

9) At cmd prompt, type: ipconfig /flushdns


Report •

Ask Question