One mans freedom fighter, another's terrorist.
Thursday, November 20, 2008
Navigation
Donate
Has this website helped you?
px
If so, please donate a little to help out with hosting costs.
Members Online
Total Online: 49
Web Spiders: 5
Guests Online: 37
Members Online: 12

Registered Members: 36791
Newest Member: infant
Most Users online: 523
Latest Articles
View Thread

HellBound Hackers | Computer General | OS specific

Page 2 of 2 < 1 2
Author

RE: Windows XP - totally fucked

hts007
Member

Posts: 782
Location:
Joined: 17.02.07
Rank:
God
Warn Level: 50
Posted on 11-07-08 04:22
can you connect via telnet??

start --> run
type cmd click ok

at the command prompt type
telnet www.google.com 80

if you can connect you'll get a blank screen, if not you'll get a prompte that say connecting to www.google.com

personnally, i would say you PC has RootKit installed on it, but that is not 100% for sure.

When the windows firewall service can't start it means that another programming is using that windows NDIS Driver shim for that service. For example, when running Routing and Remote Access (RRAS or the NAT and VPN sevice) on a windows 2003 service, you can't start the windows internet connection sharing/windows firewall service on the box.

A trojan can also cause the issue, a well designer virus will install such an NDIS driver on a PC and hide itself. When windows looks up it drivers it does so by using linked nodes......

<--Previous driver = Z(Driver a)Next driver-->B|<--previous driver=A(driver B)-->Next driver-->C|<--previous driver=B(driver C)-->Next driver=D|<--etc... etc..

A good virus will do this
<--Previous driver = Z(Driver a)Next driver-->C|<--previous driver=A(Virus driver B)-->Next driver-->C|<--previous driver=(driver C)-->Next driver=D|<--etc... etc..

In essence hidding itself from windows, because when windows enumerates its drivers it will skip from A to C, skipping B altogether.

Another issue that can cause this is DNS... but as someone suggested before ( I would image you tried it) even with DNS issues you should still be able to browse a site by it IP address, ie, for google.com http://64.233.183.99 should open google.

If ou can't use google via IP and DNS is working (start--> run Nslookup type google.com and check you get an answer) you have some deep OS issues. If telnet does not work, again OS issue (assuming you don't have a cisco router or the like blocking HTTP Traffic). Have you tried running wireshark as suggested and sniffing the packets....

I would love to troubleshoot this, very interesting issue..
Page 2 of 2 < 1 2
Guest
Username

Password

Remember Me


Bookmark This Page
Affiliates
Adverts

 


 

 


By using, viewing or obtaining any information contained on this site, you agree to the disclaimer.

© HellBound Hackers 2007- 2008. Since 3rd December 2004.