Jump to content

Justin Ewing

Active Members
  • Posts

    158
  • Joined

  • Last visited

Everything posted by Justin Ewing

  1. what programs are you ruining and where did you get that sick wallpaper
  2. Naw it was a great ending just like another typical 80 horror movie . A ending with no cause. Like another Rob zombie movie
  3. watch the strangers great scary movie
  4. this should help http://www.irongeek.com/i.php?page=compute...te-hacking-laws
  5. i guess since the show is on its yearly break.. everything seems to just slow down till the shows come back
  6. independently-funded feature film ... that pretty much says it all.. it was oook
  7. http://www.kmov.com/video/topvideo-index.html?nvid=242310 In San Francisco the "secret room" is Room 641A at 611 Folsom Street, the site of a large SBC phone building, three floors of which are occupied by AT&T. High-speed fiber-optic circuits come in on the 8th floor and run down to the 7th floor where they connect to routers for AT&T's WorldNet service, part of the latter's vital "Common Backbone." In order to snoop on these circuits, a special cabinet was installed and cabled to the "secret room" on the 6th floor to monitor the information going through the circuits. (The location code of the cabinet is 070177.04, which denotes the 7th floor, aisle 177 and bay 04.) The "secret room" itself is roughly 24-by-48 feet, containing perhaps a dozen cabinets including such equipment as Sun servers and two Juniper routers, plus an industrial-size air conditioner. The normal work force of unionized technicians in the office are forbidden to enter the "secret room," which has a special combination lock on the main door. The telltale sign of an illicit government spy operation is the fact that only people with security clearance from the National Security Agency can enter this room. In practice this has meant that only one management-level technician works in there. Ironically, the one who set up the room was laid off in late 2003 in one of the company's endless "downsizings," but he was quickly replaced by another. -- From the key ATT whistleblower in the lawsuits pending against ATT. You know that any law that would NOT grant immunity to ATT would be vetoed by the thug named Bush. When President Obama is in power, they can enact legislation to withdraw the immunity.
  8. 38 years is ridiculous... They just released a guy in Phoenix for murder and he served 12!
  9. well http://www.kood.org/windows-password-renew/ This is it, i created a new administrator account to login and change it. or Astrumi, UBCD, ERD commander
  10. Lots of options. Check some of these out and see what you're comfortable with BIG BROTHER http://www.bb4.com/ AutoNOC http://www.autonoc.com/benefits/ OpenNMS http://www.opennms.org/index.php/Main_Page Just for Fun NMS http://www.jffnms.org/ TheDude is pretty cool for a freebie... http://www.mikrotik.com/thedude.php MRTG is the defacto standard for free tool http://www.mrtg.org PRTG is a little more refined version http://www.paessler.com/prtg I'm very partial to Solarwinds Orion and the Engineer's Toolsets http://www.solarwinds.net Neon Software to diagram/document/monitor your network http://www.neon.com/map.shtml What's up gold: http://www.ipswitch.com I like the interface of Netcrunch: http://www.adremsoft.com/netcrunch/index.php Argus Sofware (looks just like What's UP Gold, only for Linux - and free) http://argus.tcp4me.com/shots.html Manage Engine by OpManager (can restart services on Windows servers) http://manageengine.adventnet.com/products...r/index.html?tb or you can use windows Network Monitor. Network Monitor is a component of the Windows Server OSs and Microsoft Systems Management Server (SMS) that lets you monitor network traffic as it crosses the wire. By using Network Monitor, you can monitor network traffic in real time or capture and store packets for later analysis. You can use the information that Network Monitor captures to troubleshoot problems on LANs, WANs, and virtually any device that uses TCP/IP to communicate. Network Monitor has three primary uses: * Troubleshooting network connectivity. This is the number-one reason to use Network Monitor. If you have two machines that have problems communicating with each other, you can use Network Monitor's Network Trace feature to help determine the problem's exact cause. You can also use Network Monitor to view each TCP/IP packet that travels between the two devices and the information contained within each packet. * Assessing network performance. Network Monitor gives you a clear picture of current network utilization. If you suspect that you have a network performance bottleneck, you can use the information that Network Monitor providessuch as detailed network-utilization statistics and information about the network traffic sourceto find the bottleneck. Although you typically won't use Network Monitor to initially identify a problem as network communications­related, it's a great second-level troubleshooting tool that can help you further pinpoint a problem and displays much more detail than Performance Monitor does. * Troubleshooting beaconing hardware devices. Before switched networks existed, you could use Network Monitor to track down problems with hardware devices on a network. You can still use Network Monitor to track fragmented or damaged packets sent out by faulty equipment, but to do so you'll probably need the full version of Network Monitor, which supports remote agents and the capture of packets on a network segment even when the traffic isn't directed to the machine that's running Network Monitor. (For more information about the two versions of Network Monitor, see the sidebar "Network Monitor Versions.") If you have a managed switch, you can use a combination of the managed-switch statistics and Network Monitor to obtain as clear a picture of the problem as possible when diagnosing faulty network hardware. Installing Network Monitor To use Network Monitor, you must have a NIC that supports promiscuous mode installed in the server that's running SMS or Network Monitor. (Most NICs support promiscuous mode.) Network Monitor isn't installed by default unless you explicitly selected it when you installed Windows Server 2003 or Windows 2000 Server. To install the version of Network Monitor that's included in Windows 2003 or Win2K Server, perform these steps: 1. Open Control Panel (click Start, highlight Settings, and click Control Panel). 2. Double-click Add or Remove Programs. 3. Click Add/Remove Windows Components. 4. Click Management and Monitoring Tools, then click Details. 5. Select the Network Monitor Tools check box and click OK. Starting Network Monitor After you've installed Network Monitor, you're ready to start the utility. Click Start, Programs, Administrative Tools, Network Monitor. (Alternatively, you can run Network Monitor from the command line or use a batch file to automate packet captures.) You'll see the initial Network Monitor screen. To start capturing packets, click the Capture button. After Network Monitor starts capturing packets. Network Monitor is the simplest utility to monitor network traffic. If you found it difficult then let me know I will suggest you a different utility. Good Luck
  11. what about going in this direction... start over and try this Obtain the IUSR account password cscript.exe adsutil.vbs get w3svc/anonymoususerpass Obtain the IWAM account password cscript.exe adsutil.vbs get w3svc/wamuserpass Set the IUSR account password cscript.exe adsutil.vbs set w3svc/anonymoususerpass "password" Set the IWAM account password cscript.exe adsutil.vbs set w3svc/wamuserpass "password" http://support.microsoft.com/default.aspx?...kb;EN-US;297989
  12. Try this mysql -u username -ppassword --batch -e "select * from mytable" mydatabase > mydata.txt or SELECT * INTO OUTFILE "c:/mydata.csv" FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"' LINES TERMINATED BY "\n" FROM my_table;
  13. Reading - Introduction to ARP Spoofing: http://packetstormsecurity.com/papers/prot...rp_spoofing.pdf The Ingredients to ARP Poison: http://www.governmentsecurity.org/articles...toARPPoison.php Tools - Plenty of tools, for all Operating systems: http://www.l0t3k.net/tools WinArpSpoof: This shows your step by step instuctions on howto test this on your network, along with the tool needed. http://www.codeproject.com/internet/winarpspoof.asp or http://www.nextsecurity.net/ That should keep you bust for a while. Good Luck,
  14. do u mean Arp Poisoning?
  15. The project is correctly building targeting 2.0. You can see this by looking at the versions of the referenced dlls. The fact it is using Csc.exe in the v3.5 folder does not mean it is not targeting the .NET *FRAMEWORK* 2.0. The version of C#, of the framework and of the runtime are independent. C# 2.0 (2005 timeframe) and 3.0 (2008 timeframe) both compile to run on the .NET 2.0 runtime and the .NET Framework 2.0, 3.0 and 3.5 all work with the .NET 2.0 runtime as well. The compiler that comes with the .NET Framework 3.5 would have various optimisations and bug fixes that means it's the best compiler to use. As the compiler that comes both with .NET Framework 2.0 and .NET Framework 3.5 compile to target the 2.0 runtime it can use the 3.5 compiler with all it's optimisations and bug fixes but instead reference the .NET Framework 2.0 dll's. I hope that makes sense :S The point of explaining all that is to point out that the problem is with the setup and deployment process, not the compilation process, just to narrow down the area you need to search for a problem. I'm not too familiar with the setup and deployment process, but I thought I'd post this now and then look so if anyone else reads this while I'm looking they too should have a clearer picture of where the problem is.
×
×
  • Create New...