1 reply to this topic

[wildweaselmi]

Here is a suggestion to find which ports needed to open on the firewall

Identifying the ports

• Start the program and try to use its network features. For example, with a multimedia program, try to start an audio stream. With a Web server, try to start the service.
  
• Click Start, click Run, type cmd, and then click OK.
  
• At the command prompt, type netstat –ano > netstat.txt, and then press ENTER. This command creates the Netstat.txt file. This file lists all the listening ports.
   netstat_2text.JPG   24.77K   0 downloads
  
• At the command prompt, type tasklist >  tasklist.txt, and then press ENTER. If the program in question runs as a service, type tasklist /svc > tasklist.txt  instead of tasklist > tasklist.txt so that the services that are loaded in each process are listed.
   tasklist_export.JPG   28.72K   1 downloads  tasklist_export2.JPG   33.17K   2 downloads
  
• Open the Tasklist.txt file, and then locate the program that you are troubleshooting. Write down the Process Identifier for the process, and then open the Netstat.txt file. Note any entries that are associated with that Process Identifier and the protocol that is used.
   tasklist_export3.JPG   78.61K   2 downloads

If the port numbers for the process are less than 1024, the port numbers will probably not change. If the numbers that are used are greater than or equal to 1024, the program may use a range of ports. Therefore, you may not be able to resolve the issue by opening individual ports.

[wildweaselmi]

if you are running Vista and get the error

Quote

x: Windows Sockets initialization failed: 5

It's a Vista issue

From Microsoft

Quote

Posted by Microsoft on 2/6/2009 at 7:13 PM
Hi, there was a bogus message print in the Vista version of netstat.exe that will display “x: Windows Sockets initialization failed: 5” everytime netstat fails to open a process handle for displaying the ownership information (needed only in the -b switch). A user mode process cannot open a handle to system process because of security reasons and netstat will display “Can not obtain ownership information” for such endpoints or connections owned by system process. The bogus error message is removed in windows 7 and you should no longer see it if you try it on Windows 7 RC builds (when they are available to you).

Thanks for reporting the problem
Ali

Microsoft solution is to give them more money for the upgraded Operating System to fix the issue with Vista.  Proof that Microsoft is forcing Vista users to upgrade because they will not support an OS that sux like Vista does.