Delphi Socket Error 10048
Contents |
goes into a FD_WAIT state. This FD_WAIT state is intended to give the socket error 10048 maya stack enough time to negotiate the final TCP/IP connection close windows socket error 10048 sequence without interference from other connections as well as preventing the close sequence from interfering with other windows socket error 10048 on api bind connections. While in FD_WAIT, you can not use that particular local port and address combination. For TIdLPR and TIdRSH, we force the client to bind to
Socket Error Errno 10048
a local port within a specific range before connecting to a server because these protocols require the client to use specific local port ranges when making a connection to a server. This is done with the TIdTCPClient.BoundPortMin and TIdTCPClient.BoundPortMax properties. Usually, if you do this with a specific IP address while a local port delphi socket error 10060 is in FD_WAIT state, the bind fails and Indy will then try to bind to the next port. Unfortunately, when using the wildcard IP address (0.0.0.0), the bind will succeed while a port is in a FD_WAIT state but when you connect, you get an "Address already in use" error. The only workarounds available are: •Wait a minute for the local port to get out of FD_WAIT state.•Set the TIdTCPClient.BoundIP property to the to the machine's current local IP address. This workaround can be problematic if a machine has more than one local IP address and you do not know which one to use. For most clients, the best practice is to let the stack select any available local port because most servers do not care what local port the client is using and because of the issue we mentioned earlier. Do not use the TIdTCPClient.BoundPort, TIdTCPClient.BoundPortMax, and TIdTCPClient.BoundPortMax properties unless you have a very compelling reason to do so.
ease planning, as well. Free PRTG Download >> What is this? This socket error 11004 delphi knowledgebase contains questions and answers about PRTG Network Monitor and
Socket Error 10061 Delphi
network monitoring in general. You are invited to get involved by asking and answering questions!
Socket Error 11001 Delphi
Learn more Top Tags 5730× prtg 1832× snmp 1462× sensor 932× wmi 621× notifications 463× maps View all Tags How do you resolve "Socket http://www.indyproject.org/kb/lprrshaddressalreadyinuse.htm Error # 10048 Address already in use" on esx server? Votes:0 Your Vote: Up Down I'm getting a "Socket Error # 10048 Address already in use." sensor error that is connect to our esx. It will go into error about every 30 minutes then clear within 20 sec. #10048 esx https://kb.paessler.com/en/topic/25253-how-do-you-resolve-socket-error-10048-address-already-in-use-on-esx-server socket-error Created on Sep 23, 2011 6:48:52 PM by tbarth (0) ●1 Permalink 1 Reply Votes:0 Your Vote: Up Down Hello, this error usually means that the PRTG Probe can't open outgoing ports anymore. Please check the Probes "Outgoing IP"-Settings in the PRTG Probe Admin tool. It might also help to use a longer scanning interval on the sensors. best regards. Add comment Created on Sep 26, 2011 12:41:32 PM by Torsten Lindner [Paessler Support] Permalink Please log in or register to enter your reply. Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available. © 1998 - 2016 Paessler AG Solutions • Imprint • Contact • Sitemap • Privacy Policy • Uninstall • Terms
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies http://stackoverflow.com/questions/7924351/can-the-indy-tidudpsever-have-multiple-instances-linked-to-the-same-udp-port-for of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask https://www.eldos.com/forum/read.php?FID=7&TID=4014 Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign socket error up Can the Indy TIdUDPSever have multiple instances linked to the same UDP Port for listening up vote 0 down vote favorite 1 I have a UDP communication system that broadcasts data messages on a single port. On a second system, I capture these messages with a TIdUDPServer component, but this application only processes a subset of the messages. When I started socket error 10048 writing a second application to process other messages in the UDP data broadcast, it works just fine. But if I try to run both applications at the same time, the second application raises the exception 'Socket Error #10048 Address already in use.' Is it possible to override/extend the Indy to allow two components to share the same UDP port for listening? delphi indy share|improve this question asked Oct 28 '11 at 1:52 Tim Koscielski 526619 What should happen then when a datagram is received? Which component should it go to? There's probably a way to do what you want to do, but you have to tell us what that is. –David Schwartz Oct 28 '11 at 1:54 I believe what some networking FAQ should be read before starting work with easy-networking components. –Premature Optimization Oct 28 '11 at 2:45 add a comment| 1 Answer 1 active oldest votes up vote 2 down vote accepted Both applications have to specify the SO_REUSEADDR flag when opening their respective sockets. Indy components have a ReuseSocket property for that purpose. However, when multiple apps are sharing
SecureBlackbox Secure storage of files and documents Solid File System Virtualization of drives, folders, files Callback File System (CBFS) CallbackDisk CallbackFilter Control over file system operations Callback File System (CBFS) CallbackFilter Control over registry operations CallbackRegistry Direct access to disks RawDisk Synchronization framework Rethync SDK Secure heterogenous messaging MsgConnect For business integrators Secure protocols for transfer and keeping of binary data, files, documents and e-mails BizCrypto for MS SQL Server BizCrypto for MS BizTalk Server Virtual drive representing remote contents of any SFTP server SFTP Net Drive Product list SecureBlackbox Security of data, files, documents and e-mails during transfer and in storages BizCrypto Security of business automation processes Solid File System Secure file and document storage Callback File System (CBFS) Virtualization of drives, folders, files CallbackDisk Virtual disk based on disk image CallbackFilter Control over file system access CallbackProcess Monitoring of process and threads creation and termination CallbackRegistry Control over registry access RawDisk Direct access to disks Rethync SDK Synchronization framework MsgConnect Secure heterogenous messaging SFTP Net Drive Mount remote SFTP storages as local drives Support options My Control Center Knowledgebase Documentation on-line Helpdesk Forum Live chat About us Corporate information Company news Testimonials Valuable clients Partner program Contact us Home / Forums / Forum «SecureBlackbox» - EldoS Topics 1 - 10 of 4045 First|Prev.|1 2345|Next|Last Topics: 4045 Topic Title Topic Starter Replies Last Post Info Pinned: Tell us what you need by Eugene Mayevski (EldoS Corp.) 0 01/03/2010 12:23:17Author: Eugene Mayevski Pinned: Books to read by Eugene Mayevski (EldoS Corp.) 0 06/08/2009 19:35:26Author: Eugene Mayevski Pinned: IMPORTANT: Read before posting by Eugene Mayevski (EldoS Corp.) 0 12/11/2007 07:23:08Author: Eugene Mayevski Pinned: Welcome to the forum by Eugene Mayevski (EldoS Corp.) 0 04/14/2006 13:30:20Author: Eugene Mayevski SSHFTPSServerDemo Limitations by Paul Stohr (Basic support level) 4 10/07/2016 20:00:39Author: Paul Stohr Loading a X509Certificate from a SmartCard into m_HTTPSClient.ClientCe by Frank Orris (Basic support level) 3 10/07/2016 16:44:10Author: Eugene Mayevski Sign XML CADES signature (.p7m ) by ntr1