Hibernation Windows Server/Client

Hibernation Enable/Disable


The hiberfil.sys file came into existence when Windows introduced a feature called hibernation. Many Windows users were initially confused by the unusual size of this mysterious file, but that is explained by how hibernation works. Hibernation is a feature that will let you save power without turning your computer off. It’s like a standby mode. It does this by momentarily freezing your system, which requires the use of memory. The memory needed to hibernate is stored in the hiberfil.sys file, which is why the file is so large. This file can be deleted from Windows Server 2008 by running a command.

To Delete Hiberfil.sys From Windows Server 2008 or Windows 7

Click on “Start,” then “Run.”

To Disable;
Type “powercfg.exe /hibernate off” and then press “Enter.”


If you want enable Hibernation type; 

Type “powercfg.exe /hibernate on” and then press “Enter.”

Windows Sysinternals Process Explorer


Ever wondered which program has a particular file or directory open? Now you can find out. Process Explorer shows you information about which handles and DLLs processes have opened or loaded.

The Process Explorer display consists of two sub-windows. The top window always shows a list of the currently active processes, including the names of their owning accounts, whereas the information displayed in the bottom window depends on the mode that Process Explorer is in: if it is in handle mode you’ll see the handles that the process selected in the top window has opened; if Process Explorer is in DLL mode you’ll see the DLLs and memory-mapped files that the process has loaded. Process Explorer also has a powerful search capability that will quickly show you which processes have particular handles opened or DLLs loaded.

The unique capabilities of Process Explorer make it useful for tracking down DLL-version problems or handle leaks, and provide insight into the way Windows and applications work.



Process Explorer can be used to track down problems. For example, it provides a means to list or search for named resources that are held by a process or all processes. This can be used to track down what is holding a file open and preventing its use by another program. Or as another example, it can show the command lines used to start a program, allowing otherwise identical processes to be distinguished. Or like Task Manager, it can show a process that is maxing out the CPU, but unlike Task Manager it can show which thread (with the callstack) is using the CPU – information that is not even available under a debugger.


  • Hierarchical view of processes.
  • Ability to display an icon and company name next to each process.
  • Live CPU activity graph in the task bar.
  • Ability to suspend selected process.
  • Ability to raise the window attached to a process, thus “unhiding” it.
  • Complete process tree can be killed.
  • Interactively alter a service process’ access security
  • Interactively set the priority of a process
  • Disambiguates service executables which perform multiple service functions. For example, when the pointer is placed over a svchost.exe, it will tell if it is the one performing automatic updates/secondary logon/etc., or the one providing RPC, or the one performing terminal services, and so on.


Download Process Explorer

Source: http://technet.microsoft.com/en-us/sysinternals

The Easiest, Fastest Way to Update or Install Software

About Ninite

Ninite was founded by Patrick Swieskowski and Sascha Kuzins. Investors include Y Combinator and a small collection of helpful angels.

Ninite is one of the best webpage for instaling programs.

You just choose what program you want to install to your computer, click to “Get installer” and install all selected programs at once.






Source: Ninite.com, Google.

HTTP Flood Denial of Service (DoS) Testing Tool for Windows

For testing purposes only

  • DoSHTTP is an easy to use and powerful HTTP Flood Denial of Service (DoS)
    Testing Tool for Windows. DoSHTTP includes URL Verification, HTTP Redirection,
    Port Designation, Performance Monitoring and Enhanced Reporting.

  • DoSHTTP uses multiple asynchronous sockets to perform an effective HTTP
    Flood. DoSHTTP can be used simultaneously on multiple clients to emulate a
    Distributed Denial of Service (DDoS) attack.

  • DoSHTTP can help IT Professionals test web server performance and evaluate
    web server protection software. DoSHTTP was developed by certified IT Security
    and Software Development professionals.


  • Easy to use and powerful HTTP Flood Denial of Service (DoS) Testing Tool
  • Uses multiple asynchronous sockets to perform an effective HTTP Flood
  • Allows multiple clients to emulate a Distributed Denial of Service (DDoS) Attack
  • Allows target port designation within the URL [http://host:port/]
  • Supports HTTP Redirection for automatic page redirection (optional)
  • Includes URL Verification that displays the response header and document
  • Includes Performance Monitoring and Enhanced Reporting
  • Allows customized User Agent header fields
  • Allows user defined Socket and Request settings
  • Supports numeric addressing for Target URLs
  • Includes a comprehensive User Guide
  • Clear Target URLs and Reset All options
  • Now supports 15,000 simultaneous connections

For testing purposes only


Windows Thin PC “MSWTPC”


Windows Thin PC enables customers to repurpose existing PCs as thin clients
by providing a smaller footprint, locked down version of Windows 7. This
provides organizations with significant benefits:

Reduced End Point costs for VDI: Windows Thin PC empowers
enterprises to leverage their end point hardware investments to access virtual
desktops that are delivered using VDI or
sessions. Windows Thin PC is available as a benefit of SA, and hence does not
represent any additional cost for SA customers. Windows Thin PC also provides IT
with the flexibility to revert back to PCs if necessary, in case the thin client
computing model does not provide the benefits they were after.

Excellent Thin Client experience: Windows Thin PC offers
many of the benefits of a thin client. Organizations can improve security and
compliance on their repurposed PCs, by using write filters to prevent data from
being written to disk. Additionally, Windows Thin PC ensures a rich remote
desktop experience through RemoteFX, enabling
delivery of high fidelity multimedia content from centralized desktops.

Enterprise Ready platform: Windows Thin PC is built on the
proven Windows 7 platform. Organizations can leverage existing management
strategy and tools such as System Center to centrally manage Windows Thin PC,
including accelerated role based deployment of applications, security patches,
updates, and data. Enterprise features such as Bitlocker
and Applocker
further help IT secure their devices, while DirectAccess
helps customers securely access their corporate data on repurposed laptops.

Microsoft recommends that customers who are currently evaluating thin client
computing begin their journey by first repurposing existing PCs as thin clients
with Windows Thin PC and evaluate the benefits they would get with this
architecture. Once Windows Thin PC device hardware get decommissioned, customers
can then purchase new Windows
Thin Clients from our OEM partners without having to make changes
to their existing management and security policies.


Windows Thin PC Quick Demo;

Windows Thin PC 2

Source: Microsoft, Youtube.

Enable GodMode in Windows 7

Windows 7’s so-called GodMode is actually a shortcut to
accessing the operating system’s various control settings.

Although its name suggests perhaps even grander capabilities, Windows
enthusiasts are excited over the discovery of a hidden “GodMode” feature that
lets users access all of the operating system’s control panels from within a
single folder.

By creating a new folder in Windows 7 and renaming it with a certain text string at
the end, users are able to have a single place to do everything from changing
the look of the mouse pointer to making a new hard-drive partition.

Enable ‘GodMode’ in Windows 7

To enter “GodMode,” one need only create a new folder and then rename the
folder to the following:


Once that is done, the folder’s icon will change to resemble a control panel
and will contain dozens of control options.



Win7, Services.msc Error prompt ActiveX

When you open Services.msc  you might get an ActiveX error message.

Open the Registry Editor and navigate to:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\

Create a Backup of the first SubKey that is not a Number (Usually a half square and just above 0) and delete it.

That’s it, now open the services.msc again and the problem is solved

Case Conficker Worm F-secure


Conficker, also known as Downup, Downadup and Kido, is a computer worm targeting the Microsoft Windowsoperating system that was first detected in November 2008.[1] It uses flaws in Windows software and dictionary attacks on administrator passwords to propagate while forming a botnet. Conficker has since spread rapidly into what is now believed to be the largest computer worm infection since the 2003 SQL Slammer,[2] with more than seven million government, business and home computers in over 200 countries now under its control. The worm has been unusually difficult to counter because of its combined use of many advanced malware techniques.

Case Conficker / Downadup
Mikko Hypponen & Patrik Runald
F-Secure Corporation

Species Conference
February 2, 2009



Part 2




Hide some file in your image (jpeg,png,…)!

!!!This tutorial is just for testing purpose!!!


So, how to hide some files in JPEG or any other image formats;



1. First you need a program called: Saint Andrew’s File in Image Hide.exe


Or you find the program using google.com 🙂


2. Run the Saint Andrew’s File in Image Hide.exe and choose you picture and file/program you want to hide in picture;


3. When you choose and click to “Add File To Image”, you will see, that your file in that case hosts.bat is hide in TestPicture.png. Below in picture you see a normal file description. !But hosts.bat file in now hide in the picture!



4. If you want Extract file back from picture, the process in very straightforward, you choose the picture, which have the file hide in picture and click to “Extract File From Image”




5. And that’s it, you have now your picture and your program/file back.



Remote Desktop Services




Remote Desktop Services

in Windows Server 2008 R2, formerly known as Terminal Services in Windows Server 2008 and previous versions, is one of the components of Microsoft Windows (both server and client versions) that allows a user to access applications and data on a remote computer over a network, using the Remote Desktop Protocol (RDP). Terminal Services is Microsoft‘s implementation of thin-client terminal server computing, where Windows applications, or even the entire desktop of the computer running Terminal Services, are made accessible to a remote client machine. The client can either be a full-fledged computer, running any operating system as long as the terminal services protocol is supported, or a barebone machine powerful enough to support the protocol (such as Windows FLP). With terminal services, only the user interface of an application is presented at the client. Any input to it is redirected over the network to the server, where all application execution takes place.[1] This is in contrast to appstreaming systems, like Microsoft Application Virtualization, in which the applications, while still stored on a centralized server, are streamed to the client on-demand and then executed on the client machine. Microsoft changed the name from Terminal Services to Remote Desktop Services with the release of Windows Server 2008 R2 in October 2009.[2] RemoteFX is being added to Remote Desktop Services as part of Windows Server 2008 R2 SP1.


Terminal Services was first introduced in Windows NT 4.0 Terminal Server Edition. It was significantly improved for Windows 2000 and Windows Server 2003. All versions of Windows XP, except Home edition, also include a Remote Desktop server. Both the underlying protocol as well as the service was again overhauled for Windows Vista and Windows Server 2008.[3] Windows includes two client applications which utilize terminal services: the first, Remote Assistance is available in all versions of Windows XP and successors and allows one user to assist another user. The second, Remote Desktop, allows a user to log in to a remote system and access the desktop, applications and data on the system as well as control it remotely. However, this is only available in certain Windows editions. These are Windows NT Terminal Server; subsequent Windows server editions, Windows XP Professional, and Windows Vista Business, Enterprise and Ultimate. In the client versions of Windows, Terminal Services supports only one logged in user at a time, whereas in the server operating systems, concurrent remote sessions are allowed.

Microsoft provides the client software Remote Desktop Connection (formerly called Terminal Services Client), available for most 32-bit versions of Windows, including Windows Mobile, and Apple‘s Mac OS X, that allows a user to connect to a server running Terminal Services. On Windows, both Terminal Services client and Remote Desktop Protocol (RDP) use TCP port 3389 by default, which is editable[4] in the Windows registry. It also includes an ActiveX control to embed the functionality in other applications or even a web page.[5] A Windows CE version of the client software is also available.[1] Server versions of Windows OSs also include the Remote Desktop for Administration client (a special mode of the Remote Desktop Connection client), which allows remote connection to the traditional session 0 console of the server. In Windows Vista and later this session is reserved for services, and users always log onto session >0. The server functionality is provided by the Terminal Server component, which is able to handle Remote Assistance, Remote Desktop as well as the Remote Administration clients.[1] Third-party developers have created client software for other platforms, including the open source rdesktop client for common Unix platforms.

For an enterprise, Terminal Services allows IT departments to install applications on a central server. For example, instead of deploying database or accounting software on all desktops, the applications can simply be installed on a server and remote users can log on and use them via the Internet. This centralization makes upgrading, troubleshooting, and software management much easier. As long as employees have Remote Desktop software, they will be able to use enterprise software. Terminal Services can also integrate with Windows authentication systems to prevent unauthorized users from accessing the applications or data.

Microsoft has a long-standing agreement with Citrix to facilitate sharing of technologies and patent licensing between Microsoft Terminal Services and Citrix XenApp (formerly Citrix MetaFrame and Citrix Presentation Server). In this arrangement, Citrix has access to key source code for the Windows platform enabling their developers to improve the security and performance of the Terminal Services platform. In late December, 2004 the two companies announced a five-year renewal of this arrangement to cover Windows Vista.



The server component of Remote Desktop Services is Terminal Server (termdd.sys), which listens on TCP port 3389. When an RDP client connects to this port, it is tagged with a unique SessionID and associated with a freshly spawned console session (Session 0, keyboard, mouse and character mode UI only). The login subsystem (winlogon.exe) and the GDI graphics subsystem is then initiated, which handles the job of authenticating the user and presenting the GUI. These executables are loaded in a new session, rather than the console session. When creating the new session, the graphics and keyboard/mouse device drivers are replaced with RDP-specific drivers: RdpDD.sys and RdpWD.sys. The RdpDD.sys is the device driver and it captures the UI rendering calls into a format that is transmittable over RDP. RdpWD.sys acts as keyboard and mouse driver; it receives keyboard and mouse input over the TCP connection and presents them as keyboard or mouse inputs. It also allows creation of virtual channels, which allow other devices, such as disc, audio, printers, and COM ports to be redirected, i.e., the channels act as replacement for these devices. The channels connect to the client over the TCP connection; as the channels are accessed for data, the client is informed of the request, which is then transferred over the TCP connection to the application. This entire procedure is done by the terminal server and the client, with the RDP protocol mediating the correct transfer, and is entirely transparent to the applications.[6] RDP communications are encrypted using 128-bit RC4 encryption. Windows Server 2003 onwards, it can use a FIPS 140 compliant encryption schemes.[1]

Once a client initiates a connection and is informed of a successful invocation of the terminal services stack at the server, it loads up the device as well as the keyboard/mouse drivers. The UI data received over RDP is decoded and rendered as UI, whereas the keyboard and mouse inputs to the Window hosting the UI is intercepted by the drivers, and transmitted over RDP to the server. It also creates the other virtual channels and sets up the redirection. RDP communication can be encrypted; using either low, medium or high encryption. With low encryption, user input (outgoing data) is encrypted using a weak (40-bit RC4) cipher. With medium encryption, UI packets (incoming data) are encrypted using this weak cipher as well. The setting “High encryption (Non-export)” uses 128-bit RC4 encryption and “High encryption (Export)” uses 40-bit RC4 encryption.


Terminal Server

Terminal Server is the server component of Terminal services. It handles the job of authenticating clients, as well as making the applications available remotely. It is also entrusted with the job of restricting the clients according to the level of access they have. The Terminal Server respects the configured software restriction policies, so as to restrict the availability of certain software to only a certain group of users. The remote session information is stored in specialized directories, called Session Directory which is stored at the server. Session directories are used to store state information about a session, and can be used to resume interrupted sessions. The terminal server also has to manage these directories. Terminal Servers can be used in a cluster as well.[1]

In Windows Server 2008, it has been significantly overhauled. While logging in, if the user logged on to the local system using a Windows Server Domain account, the credentials from the same sign-on can be used to authenticate the remote session. However, this requires Windows Server 2008 to be the terminal server OS, while the client OS is limited to Windows Server 2008, Windows Vista and Windows 7. In addition, the terminal server can provide access to only a single program, rather than the entire desktop, by means of a feature named RemoteApp. Terminal Services Web Access (TS Web Access) makes a RemoteApp session invocable from the web browser. It includes the TS Web Access Web Part control which maintains the list of RemoteApps deployed on the server and keeps the list up to date. Terminal Server can also integrate with Windows System Resource Manager to throttle resource usage of remote applications.[3]

Terminal Server is managed by the Terminal Server Manager Microsoft Management Console snap-in. It can be used to configure the sign in requirements, as well as to enforce a single instance of remote session. It can also be configured by using Group Policy or Windows Management Instrumentation. It is, however, not available in client versions of Windows OS, where the server is pre-configured to allow only one session and enforce the rights of the user account on the remote session, without any customization.


Terminal Services Gateway

The Terminal Services Gateway service component, also known as TS Gateway, can tunnel the Remote Desktop Protocol session using a HTTPS channel.[8] This increases the security of Remote Desktop Services by encapsulating the session with Transport Layer Security (TLS)[9] This also allows the option to use Internet Explorer as the RDP client.

This feature was introduced in the Windows Server 2008 and Windows Home Server products.

Important to note at the time of writing (April 2011), there are no Mac OS or Linux clients that support connecting through a Terminal Services Gateway.


Remote Desktop Connection

Remote Desktop Connection (RDC, also called Remote Desktop, formerly known as Microsoft Terminal Services Client, or mstsc) is the client application for Remote Desktop Services. It allows a user to remotely log in to a networked computer running the terminal services server. RDC presents the desktop interface (or application GUI) of the remote system, as if it were accessed locally.[1] With version 6.0, if the Desktop Experience component is plugged into the remote server, the chrome of the applications will resemble the local applications, rather than the remote one. In this scenario, the remote applications will use the Aero theme if a Windows Vista machine running Aero is connected to the server.[3] Later versions of the protocol also support rendering the UI in full 24 bit color, as well as resource redirection for printers, COM ports, disk drives, mice and keyboards. With resource redirection, remote applications are able to use the resources of the local computer. Audio is also redirected, so that any sounds generated by a remote application are played back at the client system.[1][3] In addition to regular username/password for authorizing for the remote session, RDC also supports using smart cards for authorization[1] With RDC 6.0, the resolution of a remote session can be set independently of the settings at the remote computer. In addition, a remote session can also span multiple monitors at the client system, independent of the multi-monitor settings at the server. It also prioritizes UI data as well as keyboard and mouse inputs over print jobs or file transfers so as to make the applications more responsive. It also redirects plug and play devices such as cameras, portable music players, and scanners, so that input from these devices can be used by the remote applications as well.[3] RDC can also be used to connect to WMC remote sessions; however, since WMC does not stream video using Remote Desktop Protocol, only the applications can be viewed this way, not any media. RDC can also be used to connect to computers, which are exposed via Windows Home Server RDP Gateway over the Internet. RDC can be used to reboot the remote computer with the CTRL-ALT-END key combination.



RemoteApp (or TS RemoteApp) is a special mode of Remote Desktop Services, available only in Remote Desktop Connection 6.1 and above (with Windows Server 2008 being the RemoteApp server), where remote session configuration is integrated into the the client operating system. The RDP 6.1 client ships with Windows XP SP3, KB952155 for Windows XP SP2 users,[12] Windows Vista SP1 and Windows Server 2008. The UI for the RemoteApp is rendered in a window over the local desktop, and is managed like any other window for local applications. The end result of this is that remote applications behave largely like local applications. The task of establishing the remote session, as well as redirecting local resources to the remote application, is transparent to the end user.[13] Multiple applications can be started in a single RemoteApp session, each with their own windows.[14]

A RemoteApp can be packaged either as a .rdp file or distributed via an .msi Windows Installer package. When packaged as an .rdp file (which contains the address of the RemoteApp server, authentication schemes to be used, and other settings), a RemoteApp can be launched by double clicking the file. It will invoke the Remote Desktop Connection client, which will connect to the server and render the UI. The RemoteApp can also be packaged in a Windows Installer database, installing which can register the RemoteApp in the Start Menu as well as create shortcuts to launch it. A RemoteApp can also be registered as handler for filetypes or URIs. Opening a file registered with RemoteApp will first invoke Remote Desktop Connection, which will connect to the terminal server and then open the file. Any application which can be accessed over Remote Desktop can be served as a RemoteApp.[13]

Windows 7 includes built-in support for RemoteApp publishing but it has to be enabled manually in registry, since there is no RemoteApp management console in client versions of Microsoft Windows.


Windows Desktop Sharing

Windows Vista onwards, Terminal Services also includes a multi-party desktop sharing capability known as Windows Desktop Sharing. Unlike Terminal Services, which creates a new user session for every RDP connection, Windows Desktop Sharing can host the remote session in the context of the currently logged in user without creating a new session, and make the Desktop, or a subset of it, available over Remote Desktop Protocol.[16] Windows Desktop Sharing can be used to share the entire desktop, a specific region, or a particular application.[17] Windows Desktop Sharing can also be used to share multi-monitor desktops. When sharing applications individually (rather than the entire desktop), the windows are managed (whether they are minimized or maximized) independently at the server and the client side.[17]

The functionality is only provided via a public API, which can be used by any application to provide screen sharing functionality. Windows Desktop Sharing API exposes two objects: RDPSession for the sharing session and RDPViewer for the viewer. Multiple viewer objects can be instantiated for one Session object. A viewer can either be a passive viewer, who is just able to watch the application like a screen cast, or an interactive viewer, who is able to interact in real time with the remote application.[16] The RDPSession object contains all the shared applications, represented as Application objects, each with Window objects representing their on-screen windows. Per-application filters capture the application Windows and package them as Window objects.[18] A viewer must authenticate itself before it can connect to a sharing session. This is done by generating an Invitation using the RDPSession. It contains an authentication ticket and password. The object is serialized and sent to the viewers, who need to present the Invitation when connecting.[16][18]

Windows Desktop Sharing API is used by Windows Meeting Space for providing application sharing functionality among peers; however, the application does not expose all the features supported by the API.[17] It is also used by Remote Assistance.


Source: Wikipedia


Anonymous Browsing with TOR Windows 7

What is Tor?

Tor is free software and an open network that helps you defend against a form of network surveillance that threatens personal freedom and privacy, confidential business activities and relationships, and state security known as traffic analysis.

Why Anonymity Matters

Tor protects you by bouncing your communications around a distributed network of relays run by volunteers all around the world: it prevents somebody watching your Internet connection from learning what sites you visit, and it prevents the sites you visit from learning your physical location. Tor works with many of your existing applications, including web browsers, instant messaging clients, remote login, and other applications based on the TCP protocol.

Why we need tor

Using Tor protects you against a common form of Internet surveillance known as “traffic analysis.” Traffic analysis can be used to infer who is talking to whom over a public network. Knowing the source and destination of your Internet traffic allows others to track your behavior and interests. This can impact your checkbook if, for example, an e-commerce site uses price discrimination based on your country or institution of origin. It can even threaten your job and physical safety by revealing who and where you are. For example, if you’re travelling abroad and you connect to your employer’s computers to check or send mail, you can inadvertently reveal your national origin and professional affiliation to anyone observing the network, even if the connection is encrypted.

How does traffic analysis work? Internet data packets have two parts: a data payload and a header used for routing. The data payload is whatever is being sent, whether that’s an email message, a web page, or an audio file. Even if you encrypt the data payload of your communications, traffic analysis still reveals a great deal about what you’re doing and, possibly, what you’re saying. That’s because it focuses on the header, which discloses source, destination, size, timing, and so on.

A basic problem for the privacy minded is that the recipient of your communications can see that you sent it by looking at headers. So can authorized intermediaries like Internet service providers, and sometimes unauthorized intermediaries as well. A very simple form of traffic analysis might involve sitting somewhere between sender and recipient on the network, looking at headers.

But there are also more powerful kinds of traffic analysis. Some attackers spy on multiple parts of the Internet and use sophisticated statistical techniques to track the communications patterns of many different organizations and individuals. Encryption does not help against these attackers, since it only hides the content of Internet traffic, not the headers.

Staying anonymous

Tor can’t solve all anonymity problems. It focuses only on protecting the transport of data. You need to use protocol-specific support software if you don’t want the sites you visit to see your identifying information. For example, you can use Torbutton while browsing the web to withhold some information about your computer’s configuration.

Also, to protect your anonymity, be smart. Don’t provide your name or other revealing information in web forms. Be aware that, like all anonymizing networks that are fast enough for web browsing, Tor does not provide protection against end-to-end timing attacks: If your attacker can watch the traffic coming out of your computer, and also the traffic arriving at your chosen destination, he can use statistical analysis to discover that they are part of the same circuit.

Configuring Windows 7 to browse with TOR:

1. Go to website of tor project; https://www.torproject.org/

2. Clik to Download stable TOR;

3. Click to open downloaded .exe file, to start the setup;

4. When install leave default “FULL” instalation;

5.  Open the new installed program “VIDALIA”  and click on “Start Tor”

In 10-15 second you will be connected to TOR;

6. If you have some problem with default TorButton, check this;

Go to https://www.torproject.org/torbutton/ and install the stable TorButton; Firefox 5.0!

7. When TorButton install is finish, restart Firefox an you’ll see the new TorButton;

8. Click to this new button and choose “Toggle Tor Status”;

The Tor is now enabled in your browser, you see the green color on the TorButton;

9. Now TOR is started, as you can see on step 5. and you enable the tor for your browser “Firefox” with TorButton.

Now you can start your browsing through the internet and change your identity bi clicking “Use a New Identity” to change your IP address.

Every time you click on “Use a New Identity” you will get the different IP Address in Firefox, if  TOR is enabled.

If you want to test your IP Address, go to http://www.whatismyip.com/ and you will see, what is your current IP Address when you browsing through the internet with your Firefox Browser.

For more information; https://www.torproject.org/

Disable NetBIOS over TCP/IP in Windows 7 ent.

NetBIOS over TCP/IP (NBT, or sometimes NetBT) is a networking protocol that allows legacy computer applications relying on the NetBIOS API to be used on modern TCP/IP networks.

NetBIOS was developed in the early 1980s, targeting very small networks (about a dozen computers). Some applications still use NetBIOS, and do not scale well in today’s networks of hundreds of computers when NetBIOS is run over NBF. When properly configured, NBT allows those applications to be run on large TCP/IP networks (including the whole Internet, although that is likely to be subject to security problems) without change.

NetBIOS provides three distinct services:

  • Name service for name registration and resolution (port: 137)
  • Datagram distribution service for connectionless communication (port: 138)
  • Session service for connection-oriented communication (port: 139)

If you want disable NetBIOS over TCP/IP you take the following steps:

1. Right click to your network interface at the right down corner:

2. Choose “Open Network And Sharing Center”

3. Next click to “Change Adapter Settings”

4. Right click on your network adapter and choose “Properties”

5.  On your network adapter click to “Internet Protocol Version 4” and Properties.

6. When you open the “Properties” you hit on button “Advanced”

7. When you click to Advanced button, Windows will open “Advanced TCP/IP Settings”

In that last window you click on “WINS” tab and then choose “Disable NetBIOS over TCP/IP”

And NetBIOS over TCP/IP is Disabled.