Jump to content

  • Log In with Google      Sign In   
  • Create Account

#ActualKhatharr

Posted 06 July 2013 - 09:37 PM

The send operation locally completes without problems, but the network later returns an ICMP packet indicating that the destination is invalid. Subsequent socket operations will report that error state.

 

How you deal with this message is up to you, depending on what you're doing. The message does indicate that your intended destination is not receiving your packets, so usually you'd want to take that into consideration.

 

If you're getting this error on the loopback it suggests that you haven't correctly bound the listening socket prior to calling sendto.

 

 

 

 

NVM, after looking around a bit this is a spurious message in this case. Just ignore it.


#5Khatharr

Posted 05 July 2013 - 06:47 PM

The send operation locally completes without problems, but the network later returns an ICMP packet indicating that the destination is invalid. Subsequent socket operations will report that error state.

 

How you deal with this message is up to you, depending on what you're doing. The message does indicate that your intended destination is not receiving your packets, so usually you'd want to take that into consideration.

 

If you're getting this error on the loopback it suggests that you haven't correctly bound the listening socket prior to calling sendto.

 

 

 

 

NVM, after looking around a bit this is a spurious message in this case. Just ignore it.


#4Khatharr

Posted 05 July 2013 - 06:40 PM

The send operation locally completes without problems, but the network later returns an ICMP packet indicating that the destination is invalid. Subsequent socket operations will report that error state.

 

How you deal with this message is up to you, depending on what you're doing. The message does indicate that your intended destination is not receiving your packets, so usually you'd want to take that into consideration.

 

If you're getting this error on the loopback it suggests that you haven't correctly bound the listening socket prior to calling sendto.


#3Khatharr

Posted 05 July 2013 - 06:40 PM

The send operation locally completes without problems, but the network later returns an ICMP packet indicating that the destination is invalid. Subsequent socket operations will report that error state.

 

How you deal with this message is up to you, depending on what you're doing. The message does indicate that your intended destination is not receiving your packets, so usually you'd want to take that into consideration.

 

If you're getting this error on the loopback it suggests that you haven't correctly bound the listening socket prior to calling sendto.


#2Khatharr

Posted 05 July 2013 - 06:39 PM

The send operation locally completes without problems, but the network later returns an ICMP packet indicating that the destination is invalid. Subsequent socket operations will report that error state.

 

How you deal with this message is up to you, depending on what you're doing. The message does indicate that your intended destination is not receiving your packets, so usually you'd want to take that into consideration.


#1Khatharr

Posted 05 July 2013 - 06:37 PM

The sendto puts the socket in an error state when it determines that it can't complete. The subsequent call will report that error. This is because the send operation locally completes without problems, but the network later returns an ICMP packet indicating that the destination is invalid.

 

How you deal with this message is up to you, depending on what you're doing. The message does indicate that your intended destination is not receiving your packets, so usually you'd want to take that into consideration.


PARTNERS