Results 1 to 2 of 2

Thread: Winsock error 10049: Address not available

  1. #1

    Thread Starter
    Hyperactive Member
    Join Date
    Apr 1999
    Location
    Prague, Czech Republic
    Posts
    350
    I get this error whenever I try to connect to any address. What to do with it? Any other applications using WinSock has not troublues...

  2. #2
    Guru Yonatan's Avatar
    Join Date
    Apr 1999
    Location
    Israel
    Posts
    892
    Originally written in MSDN

    WSAEADDRNOTAVAIL (10049)
    Cannot assign requested address.
    The requested address is not valid in its context. Normally results from an attempt to bind to an address that is not valid for the local machine, or connect/sendto an address or port that is not valid for a remote machine (e.g. port 0).
    This means:
    When you connect to an address, you cannot connect to port 0. You must select a more "normal" port.
    The port depends on what you need it for. The most common ones are 23 (telnet), 21 (FTP) and 80 (HTTP).

    Set the RemotePort property of the Winsock control to the wanted port before using the Connect method.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width