jblosser

Coming from the 'yellow knee-length underwear wearing Kid', that's rich...

:white flag smilie:

You had already checked the things and attempted fixes that would have fixed 95% of Windows <whatever version> problems. Under the hood/beyond the visual stuff, 7 is not that different from XP - at least in the basic 'way things work', e.g. the hosts file is still there, command line commands are all still there (with some new ones). Now, Active Directory 2008 versus 2003, or Exchange 2010 versus 2007, there are major differences. Had my fill of fun today to last me all year...

Now we're cooking!

should work, they're both NTFS. If you have a way to get any wanted data off the drive - like hooking it to another computer as you're thinking of doing - it might just be easiest/quickest to grab what you want off of it, then wipe the sucker out and reinstall Windows. Or, better yet, install Linux...

Very good idea. If a full scan (make sure your AV is up to date, duh) finds nothing, could try Rootkit Revealer (click, link at MS Technet)

Might work: When did IE last work properly? We want to search for files/folders created after that time. Could try going to the Control Panel, Programs, and see if something's in there that you don't recognize. Long shot, but possible. Press the Windows key plus F (to bring up the search function), choose Files Changed Since This Date (or whatever it's called - at home on my Linux laptop now) and let Windows search. You <should/maybe> find at least one folder with a suspicious name, probably won't be able to delete it, assuming there's at least one file in there that's loaded in memory, and not allowing you out to the Internet.

Try Start, Programs, Accessories, right click Command Prompt and choose Run As Administrator, then try the "at" command again. Probably nothing, but worth looking at.

If you try Tom's 'pull the battery' idea (which is a good idea, btw), upon restarting we could try going into 'safe mode with networking' by pressing F8 once you see the BIOS screen. If you see the Windows logo, you are too late, power it off, on and press F8 sooner.

Since I ran into this yesterday on two servers that McAfee and MBAM said were "fine" but had obvious things wrong with them: From a command prompt, type "at" and hit enter, normally you shouldn't have any scheduled tasks, unless you set something up via the task scheduler. <Might> be something there which <might> be causing your troubles.

DNS is working. Your network is working. Everything's fine, except you can't get out to teh intarwebz through either connectivity option on the one laptop. Sooo. I would think that IE is hosed and that another browser would work, except that Firefox is broken, too. If you have a thumb drive maybe try grabbing HiJack This (click) (link hosted at MajorGeeks.com, d/l should start automatically), install it on the laptop, run it, select the first option "Do a system scan and save a logfile", then PM the logfile to me (if you post it up here it'll take up a whole page). I'll see if anything stands out like a sore, umm, thumb. While you're waiting on the d/l (it's not very big), if your laptop is still wired in, try disabling the wireless (there should be a switch somewhere), see if that makes any difference... I doubt it, but it might. I'm heading out of the data center and going home, so I'll check back in in 30 minutes or so.

lulz at thread tags...

In IE: Tools Internet Options Connections (tab up at top) LAN Settings (button, lower right)

Yeah, you would be, I think he stumbled upon the WOW64 folder while looking for his hosts file, and wondered what it is. If his \system32 folder had gone bye-bye, he wouldn't be able to boot the machine, so he'd have much bigger issues than stupid IE not cooperating.

So, from the command line are you still able to ping Google (or anything)? And to clarify, other machines on your network are are able to get out using the same method (wireless, assuming that the 'broken' lapper is going out via wireless). If you have a spare Ethernet cable, try plugging the lapper into your router, maybe do an "ipconfig/release" and "ipconfig/renew" just for yuks, restart IE (or Firefox), and see what happens. Also, in IE, click Tools, Internet Options, click the Connections tab, click LAN Settings, and make sure that the "Use automatic config...." and "Use a proxy server..." boxes are not checked. Again, I'm guessing that you're not running your own proxy server at home... Assuming you try all of the above and shit still ain't working, turn off the laptop, let it set for a moment, power it back on, see what happens. I know, I know, you already tried rebooting, but it's Windows. If a reboot doesn't cure it...

The \sysWOW64 folder is supposed to be there, no worries. You should still have a \system32 folder. Just to confuse you: - On 64-bit Windows, the \System32 folder contains 64-bit binaries (programs). - The \sysWOW64 folder contains 32-bit versions of the binaries found in the \system32 folder. "WOW64" stands for "Windows On Windows 64-bit. Clear as mud?

:lol: you think of those all by yourself, Chebby? +REP for you, witty one...!

I'll go out on a limb here and guess you're not doing your own DNS hosting, so go to the tcp/ip properties, go ahead and check the "Use the following DNS...", put in the two Google Public entries, Apply, OK, restart IE, see if that doesn't fix it.

from the command line (DOS), try without the quotes "ipconfig /all", make sure that there is at least one entry for "DNS Servers", and it/they should not be from your network, in other words not 192.xxx.xxx.xxx If none are listed, go back to your tcp/ip settings for (I'm assuming) the wireless card, check the box "Use the following DNS server..." and put 8.8.8.8 and 8.8.4.4 (Google Public DNS) in the Preferred and Alternate DNS Server boxes. Also, remember that, at least with IE, any changes you make to the network settings or LAN Connection settings require you to restart IE. Firefox/Chrome (Mozilla) don't need restarted.

Yeah, Dwight, I got it... I was tryin' to be funny, yo, tryin' to represent. Why you gotta be dissin' me like that? I have no idea what I just said...

In Win 7 your hosts (not lmhost) file is at c:\windows\system 32\drivers\etc Since you can ping from the command line, your tcp/ip settings are good. Try putting 67.231.21.21 (ORdN) in the address box in IE or Firefox, tell us what happens.

Thread: (talking about guns) Jagr: "There's a huge number of yeast infections in this country" Meanie: "Yeast infections?" Me: "Forget it, he's rolling"

Meh, you'll have that... Keep up the good work, and thanks for all you do!