Solved

Winsock error: "Only one usage of each socket address ..."

Posted on 2004-09-26
2
543 Views
Last Modified: 2008-02-01
Hi all:

I recently moved from Windows XP Home to XP Professional, transferred my data and reinstalled my programs.  Everything was peachy until I reinstalled an SSH tunnelling application I had used with XP Home.  This program basically forms a tunnel between my computer and a remote server and handles requests passed via specific ports (usually 25, 80, 110 and 119).  But ever since trying it on XP Pro the program I use (F-Secure) has been unable to initialize these ports (25, 80, 110 and 119).  (I manage to create a tunnel to 110 and 119 but that's still of limited use.)  The program's listening manager returns the standard WSAEADDRINUSE 10048 error: "Only one usage of each socket address (protocol/IP address/port) is normally permitted".

No, I know none of *my* programs usurp these ports and since I have no viruses, I can only assume programs and/or processes inbuilt in Win XP PRO are responsible.  I know XP Professional uses additional network components but since this is not my area of expertise, I don't know which they are, let alone which may be responsible for hogging these ports.  So, how can I identify applications or processes usurping these ports and, more importantly, shut them down permanently?  Any ideas?

Thanks.

Michael
0
Comment
Question by:lordgovernor
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 15

Accepted Solution

by:
adamdrayer earned 250 total points
ID: 12156489
you can monitor your open ports with this:
http://www.sysinternals.com/ntw2k/source/tcpview.shtml

or you can also type "netstat" at a command prompt.

ICF or "Windows Firewall" might be responsible for that error message.  Verify that you don't have any software firewalls blocking access to those ports including the built-in one for windows which often turns itself on during an installation.
http://www.practicallynetworked.com/sharing/xp/ic_firewall.htm

If you've tried everything, and are sure there is no program using or blocking that particular TCP port, and still cannot get this to work, you may want to rebuild your winsock.  you can do that here:
http://www.spychecker.com/program/winsockxpfix.html
0
 

Author Comment

by:lordgovernor
ID: 12156775
Hi Adam:

The TCPview identified Internet Information Services as "listening" on my ports and preventing SSH from being established thru them.  (It's precisely what I had suspected: XP Pro has a built-in server.)  I ended up downloading a utility from Microsoft which turned IIS off.  It can be found here: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=DDE9EFC0-BB30-47EB-9A61-FD755D23CDEC

Thanks for your help!

Best regards,
Michael
0

Featured Post

Instantly Create Instructional Tutorials

Contextual Guidance at the moment of need helps your employees adopt to new software or processes instantly. Boost knowledge retention and employee engagement step-by-step with one easy solution.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Nslookup is a command line driven utility supplied as part of most Windows operating systems that can reveal information related to domain names and the Internet Protocol (IP) addresses associated with them. In simple terms, it is a tool that can …
Sometimes you might need to configure routing based not only on destination IP address, but also on a combination of destination IP address (or hostname) and destination port number. I will describe a method how to accomplish this with free tools. …
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …
Suggested Courses

623 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question