Light blog

Archive for the ‘Windows’ Category

greetings to: http://www.arcengames.com/forums/index.php?topic=2055.0

Problem

Unable to connect to other games with Hamachi on Windows 7, and everything else is set as accordingly (port forwarded, firewall exceptions, etc.).

In interest, I upgraded from Vista Ultimate X64 to Windows 7 Ultimate X64. I have a router that is properly configured, and of which Hamachi was functioning properly prior to the upgrade.

Solution

The problem apparently is something to do with the way Windows 7 broadcasts packets–basically, something to do with “Interface metric”. Please see below for the lore and solution.

http://logmeinwiki.com/wiki/Hamachi:Gaming_over_Hamachi

* Windows 7 Notes (RC7100)

Windows 7 appears to send broadcast packets (packets destined for 255.255.255.255) out the interface associated with the broadcast route having the lowest metric. It does this regardless of the order of the interfaces in the “Advanced Settings” menu. If there is more than one broadcast route with the same metric, it sends it out the first one. NOTE: When a new interface comes up, it’s broadcast route gets added to the end of the list. Broadcast routes are the last routes listed in the route list produced with the ‘route print’ command. To summarize, here is how it chooses which interface to send packets destined for 255.255.255.255:

1. It looks at the metrics associated with all “255.255.255.255 mask 255.255.255.255″ routes. If one is lower than all the others, it sends the packet out that interface.
2. If there is “tie” for the lowest metric, it sends it out the first one in the tie.

The metric associated with the Hamachi broadcast route can be lowered to be the lowest in the list of broadcast routes when running Hamachi 2 (tested with 2.0.1.64). By default, Hamachi installs with a metric of ’9000′ associated with it’s interface. In Windows 7, if you change the metric to ’1′ you’ll end up a metric of 257 associated with these routes (256 + ’1′). This will be lower than the default LAN interface metric and broadcast packets will now go out the Hamachi interface. NOTE: This is only affecting broadcast packets.

This shouldn’t interfere with or affect any of your other network connections – but use at your own risk.

1. Go to the properties of the Hamachi adapter
2. Select ‘Internet Protocol Version 4) and click ‘Properties’
3. Click ‘Advanced’
4. Change the ‘Interface metric’ at the very bottom from 9000 to 1
5. Disable and re-enable the interface (or reboot)

If you look at the route list now (‘route print’) you should see the broadcast route associated with the Hamachi interface now has a metric lower than any of the other broadcast routes. Broadcast packets will now go out the Hamachi interface.

Quick Solution

http://rp-mods.com/Forum/wbb/hardware-software/6071-hamachi-network-fix/

Change the Interface Metric for Hamachi:

* Start -> “run”
* “ncpa.cpl” then ENTER.
* Right click on “Hamachi” and PROPERTIES
* Deactivate “Internetprotocol Version 6 (TCP/IPv6)”
* “Internetprotocol Version 4 (TCP/IPv4)” -> PROPERTIES -> Advanced
* Interface metric to “10″.
* Hamachi Gateway 5.0.0.1 Metric to “1500″.

Remember to also have your Hamachi set as the foremost network to use after an upgrade/clean install.

Change the Priority of Hamachi Adapter

* Start -> “run”
* “ncpa.cpl” then ENTER.
* Press [ALT]-Key (Menu appears)
* Advanced -> Advanced Properties
* Move Hamachi to the top of the list
* Restart PC.

Hope it works for you–took me heck of a long time Googling in discovering this. If not… hopefully Hamachi developers are working on a universal solution to compatibility issues with Windows 7, even though they say it is compatible with the OS.

Problem: trying to run apache or other application server on port 80, but port 80 is being in use.
If you run in a command window the command: “netstat -aon” and you get:   TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 4
In process task manager, PID 4 is SYSTEM, which is not really helpful, because there are more windows application which can use that port.

In this case, you should verify for the following things:

1. check if Skype is started, in this case close it

2. check if IIS (Internet Information Services) is started, if so, then stop the it from Control Panel -> Administrative Tools -> Internet Information Services (IIS) Manager,
or from command line :  NET STOP IISADMIN /Y

3. check if SQL Server Reporting Services (MSSQLSERVER) is started, in the windows services, if so stop it

Bonjour enables automatic discovery of computers, devices, and services on IP networks.
Bonjour uses industry standard IP protocols to allow devices to automatically discover each other without the need to enter IP addresses or configure DNS servers.

If you have installed software by Apple such as iTunes, software by Adobe such as Premiere Pro, Skype, Gizmo, chances are there’s already a Bonjour folder in your Program Files.
This service starts automatically and runs a process named mDNSResponder.exe.
If you do not want Bonjour to be in your computer and want to uninstall it,

here’s how to uninstall Bonjour and remove mDNSResponder.exe

1. Go to Start > Run > type the command below and hit OK.
cmd

next, move to the Bonjour folder in program files, typing:

cd\programfiles\bonjour

now type:
mDNSResponder.exe -remove

2. Navigate to C:\Program Files\Bonjour
3. Rename the mdnsNSP.dll file in that folder to mdnsNSP.old
4. Restart your computer
5. Delete the Program Files\Bonjour folder

Manual steps to recover from Winsock2 corruption
Windows XP with Service Pack 2 instructions
To repair Winsock if you have Windows XP Service Pack 2 (SP2) installed, type netsh winsock reset at the command prompt, and then press ENTER.

Note Restart the computer after you run this command. Additionally, for computers that are running Windows XP SP2, there is a new netsh command that can rebuild the Winsock key. For more information, visit the following Web site:
http://technet.microsoft.com/en-us/library/bb457156.aspx (http://technet.microsoft.com/en-us/library/bb457156.aspx)
Warning Programs that access or monitor the Internet such as antivirus, firewall, or proxy clients may be negatively affected when you run the netsh winsock reset command. If you have a program that no longer functions correctly after you use this resolution, reinstall the program to restore functionality.

Note If these steps do not resolve the problem, follow the steps in the next section.

Windows XP without Service Pack 2 instructions

To repair Winsock if you do not have Windows XP SP2 installed, delete the corrupted registry keys, and then reinstall the TCP/IP protocol.
Step 1: Delete the corrupted registry keys
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 (http://support.microsoft.com/kb/322756/) How to back up and restore the registry in Windows

For more information about how to back up the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 (http://support.microsoft.com/kb/322756/) How to back up and restore the registry in Windows XP and Windows Vista
1. Click Start, and then click Run.
2. In the Open box, type regedit, and then click OK.
3. In Registry Editor, locate the following keys, right-click each key, and then click Delete:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2
4. When you are prompted to confirm the deletion, click Yes.
Note Restart the computer after you delete the Winsock keys. Doing so causes the Windows XP operating system to create new shell entries for those two keys. If you do not restart the computer after you delete the Winsock keys, the next step does not work correctly.
Step 2: Install TCP/IP
1. Right-click the network connection, and then click Properties.
2. Click Install.
3. Click Protocol, and then click Add.
4. Click Have Disk.
5. Type C:\Windows\inf, and then click OK.
6. On the list of available protocols, click Internet Protocol (TCP/IP), and then click OK.

If Internet Protocol (TCP/IP) does not appear, follow these steps:
a. Click Start, and then click Search.
b. In the Search Companion pane, click More advanced options.
c. Click to select the following three check boxes:
• Search system folders
• Search hidden files and folders
• Search subfolders
d. In the All or part of the file name box, type nettcpip.inf, and then click Search.
e. In the results pane, right-click Nettcpip.inf, and then click Install.
7. Restart the computer.