| Dart Home | PowerTCP Winsock for ActiveX | Custom Development | Reply | PowerTCP Winsock for ActiveX Topics | Forums |
| Author | Forum: PowerTCP Winsock for ActiveX Topic: Windows2003, Windows XP |
| Weninger From: Vienna, AL Austria Posts: 5 Member Since: 05/03/03 |
posted September 15, 2003 6:10 AM I wrote a program which consists of two parts: a server application and a client application. The communicate via winsock control. Everything works fine, when i run the client on computer a and the server on computer b. When i run both apps on ONE computer I encountered problems in the communication on windows 2003 and windows xp sp1 (windows xp without sp1 works fine!). On these OS I get some error messages (tcp port is already used; connection blocked, ...) which I don't get when the apps are running on different computers or running under windows2000 on the SAME computer. Has someone any idea? |
Tony Priest From: Utica, NY USA Posts: 8466 Member Since: 04/11/00 |
posted September 15, 2003 8:49 AM It sounds like you already have a server running on the machine you are having problems with. Please give the exact steps we need to take with our echo server sample on an XP machine so that we can see the behavior. |
| Weninger From: Vienna, AL Austria Posts: 5 Member Since: 05/03/03 |
posted September 25, 2003 4:24 AM The problem is, that the erros are not reproducable. Some times i get one when I log in to my server app, some times i don't. Seems to me, as if it is a timing problem. Maybe there is a general setting (for tcp?) which should be set... |
| Weninger From: Vienna, AL Austria Posts: 5 Member Since: 05/03/03 |
posted September 25, 2003 4:28 AM AddOn: One of the error messages i encounter frequently is the following: Connect, listen or open method failed. Only one use of each socket address (protocol/IP address/port) is normally permitted.... consider using setsockopt(SO_REUSEADDR). But I am not using sockets more than once. Any idea? |
| Tony Priest From: Utica, NY USA Posts: 8466 Member Since: 04/11/00 |
posted September 25, 2003 8:50 AM That error can occur in the following scenarios: 1) You are attempting to start a daemon on a port when another server is already using it. Example, you try to listen on port 80 or 443 when you have IIS running. 2) You are attempting to start a daemon that you previously closed, but there are still spawned clients connected. Use ReuseAddr to fix that. 3) You are attempting to connect to a remote server and you specified a local port in the connect method that is already in use. To remedy that, use 0 as the localport so that it will be automatically chosen. If neither of those apply to your situation, then you will have to isolate this down to something reproducible. |
| Reply | PowerTCP Winsock for ActiveX Topics | Forums |
This site is powered by
PowerTCP WebServer for ActiveX
|