Forum

Results 1 to 5 of 5
  1. #1
    Join Date
    February 2003
    Location
    NJ/USA
    Posts
    4

    Unhappy Socket Error # 10049

    Below is a sample of the errors that I am getting. I am presuming that this is the cause of my extreme packet loss even though I have a really nice low ping. Does anyone have any ideas what this is and why its happening?

    The first one with the or's is repeated three times in different places, the rest are all the same..

    Thanks in advance for any help..


    06-02-03 17:37:56,2304,WARNING,All,procedure TDICallBack.execute,"The operation had no effect." or "The device buffer overflowed and some input was lost." or "The device exists but is not currently attached." or "The change in device properties had no effect."
    06-02-03 17:37:56,2740,WARNING,All,procedure TClientWriteThread.Execute,Socket Error # 10049
    Cannot assign requested address.
    06-02-03 17:37:56,2740,WARNING,All,procedure TClientWriteThread.Execute,Socket Error # 10049
    Cannot assign requested address.
    06-02-03 17:37:56,2740,WARNING,All,procedure TClientWriteThread.Execute,Socket Error # 10049
    Cannot assign requested address.
    06-02-03 17:37:57,2740,WARNING,All,procedure TClientWriteThread.Execute,Socket Error # 10049
    Cannot assign requested address.
    06-02-03 17:37:57,2740,WARNING,All,procedure TClientWriteThread.Execute,Socket Error # 10049
    Cannot assign requested address.
    06-02-03 17:37:57,2740,WARNING,All,procedure TClientWriteThread.Execute,Socket Error # 10049
    Cannot assign requested address.
    06-02-03 17:37:57,2740,WARNING,All,procedure TClientWriteThread.Execute,Socket Error # 10049
    Cannot assign requested address.
    06-02-03 17:37:57,2740,WARNING,All,procedure TClientWriteThread.Execute,Socket Error # 10049
    Cannot assign requested address.
    06-02-03 17:37:59,2740,WARNING,All,procedure TClientWriteThread.Execute,Socket Error # 10049
    Cannot assign requested address.
    06-02-03 17:38:00,2740,WARNING,All,procedure TClientWriteThread.Execute,Socket Error # 10049
    Cannot assign requested address.
    06-02-03 17:38:00,2740,WARNING,All,procedure TClientWriteThread.Execute,Socket Error # 10049
    Cannot assign requested address.

  2. #2
    Join Date
    February 2003
    Location
    NJ/USA
    Posts
    4
    Found this for the meaning of the error code in winsock.

    Now if someone could just help me figure out why I'm getting it.

    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/sendtoan address or port that is not valid for a remote machine (e.g. port 0).

  3. #3
    Join Date
    February 2003
    Location
    NJ/USA
    Posts
    4
    Figured it out.

    I put the host for our ts server in the firewall on my machine (Norton Firewall for me) and now I dont get the errors anymore and I get zero percent packet loss.

    Someone please add this to a q&a I bet others will have this problem too.

    It comes up a lot in client server apps and I totally forgot about it until I remembered I ahd the same problem with earth and beyond.

  4. #4
    Join Date
    June 2003
    Location
    Michigan
    Posts
    1
    27-06-03 01:10:26,ALL,Info,server, Server init initialized
    27-06-03 01:10:26,ALL,Info,server, Server version: 2.0.19.40 Win32
    27-06-03 01:10:26,ALL,Info,server, Starting server with port: 8767
    27-06-03 01:10:26,ERROR,All,SERVER, Server startup failed with port 8767, Exception: EIdSocketError.Socket Error # 10049
    Cannot assign requested address.
    27-06-03 01:10:26,ERROR,All,WEBINTERFACE, WebInterface startup failed with port 14534, Exception:Socket Error # 10049
    Cannot assign requested address.
    27-06-03 01:10:26,ERROR,All,TCPQUERY, TCPQuery startup failed with port 51234, Exception: Socket Error # 10049
    Cannot assign requested address.
    27-06-03 01:10:26,ALL,Info,server, Server init finished
    27-06-03 01:17:53,ALL,Info,server, Server shutdown initialized
    27-06-03 01:17:54,ALL,Info,server, Server shutdown finished

    Ok mine is a little different, this is from the server log-I've been running Teamspeak (awesome program) on a machine behind the same router for awhile with no problem, as soon as I moved it to another machine on the same router I started getting this error above and no one can connect-Help please?

  5. #5
    Join Date
    September 2003
    Location
    TN, USA
    Posts
    5

    forward port

    i think u need to forward the port (8767) on your router to the internal ip of the new pc that the program is now running on, i beleive that will fix the problem!

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

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