Hello !

I have an application, written in XBase++/Asinet that listens on port 99.

The server (box) is running for 25/26 days.

The application was running fine too. However, since I needed to update its 
EXE, I simply quitted it, updated its EXE and started it again.

It can no longer run, however because SOCKETLISTEN is issuing error 10038.

The changes I've made to the EXE are simply related to a console display 
output. Nothing related to its internal mechanism, which has been stable.

Using TCPVIEW, from SysInternals, I can see that there's a process called 
"system", with pid 8, which is having my port 99 opened.

Have you ever faced such situation ? I'm about to boot the server but I think 
this is a pitty because everything else is working fine there.

thanXs in advance for your suPPort !

Jose Adriano Baltieri wrote:

> I have an application, written in XBase++/Asinet that listens on port 99.

ports below 1024 are so-called "well known ports", normally you should not
use them for any other purpose than what they are reserved... see
http://www.iana.org/assignments/port-numbers for more info.

> It can no longer run, however because SOCKETLISTEN is issuing error 10038.

See

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winsock/winsock/windows_sockets_error_codes_2.asp

for the meaning of this error... from your description a different process
seems to have "hijacked" your port 

> Have you ever faced such situation ? I'm about to boot the server but I think
> this is a pitty because everything else is working fine there.

Most likely you will have not other chance (or use TCPView to close socket
on port 99)

regards
Thomas Braun

web: www.software-braun.de / email: nospam@wegasoft.de
If you need to send email, substitute "nospam" with my initials
since the spam account is not checked on a regular basis.
Xbase++ FAQ : http://faq.xbasecentral.net

Thomas Braun wrote:
> Jose Adriano Baltieri wrote:
> 
> 
>>I have an application, written in XBase++/Asinet that listens on port 99.
> 
> 
> ports below 1024 are so-called "well known ports", normally you should not
> use them for any other purpose than what they are reserved... see
> http://www.iana.org/assignments/port-numbers for more info.

OK. But the same problem started to happen with my FTP server as well. Same 
symptom...
> 
> 
>>It can no longer run, however because SOCKETLISTEN is issuing error 10038.
> 
> 
> See
> 
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winsock/winsock/windows_sockets_error_codes_2.asp
> 
> for the meaning of this error... from your description a different process
> seems to have "hijacked" your port 

Yes. And the process who did it is called "system" ! , with pid 8
> 
> 
>>Have you ever faced such situation ? I'm about to boot the server but I think
>>this is a pitty because everything else is working fine there.
> 
> 
> Most likely you will have not other chance (or use TCPView to close socket
> on port 99)

The problem is that even using TCPView and asking it to close that port, it 
wont....
> 
> regards
> Thomas Braun

After all, what I had to do was to boot the whole system.

But, unfortunatelly, this is pretty bad.
I know this is not an Asinet/Xbase++ problem but, since this may be a problem 
for our community....

Jose,

> The application was running fine too. However, since I needed to update its 
> EXE, I simply quitted it, updated its EXE and started it again.
> 
> It can no longer run, however because SOCKETLISTEN is issuing error 10038.

...and that was your mistake.  You need to ensure the socket is properly
closed, otherwise it will remain open, even though you do not have an
application attached to it to handle it.

Remember that the socket is created and administered by a system
application (wininet.dll), to which you only have an API.

Regards,

Phil Ide

***************************************
* Xbase++ FAQ, Libraries and Sources: *
* goto: http://www.idep.org.uk/xbase  *
***************************************

I was the next door kid's imaginary friend.

Well, I guess I've found a possible cause for this problem : a trojan horse.

Running anti-virus on my server, it found a Windows DLL infected with it.

Now I've got to wait and see how long server will stand without having to be 
booted again.

thanXs for all suPPort I've had from this NG !

Jose Adriano Baltieri wrote:
> Hello !
> 
> I have an application, written in XBase++/Asinet that listens on port 99.
> 
> The server (box) is running for 25/26 days.
> 
> The application was running fine too. However, since I needed to update 
> its EXE, I simply quitted it, updated its EXE and started it again.
> 
> It can no longer run, however because SOCKETLISTEN is issuing error 10038.
> 
> The changes I've made to the EXE are simply related to a console display 
> output. Nothing related to its internal mechanism, which has been stable.
> 
> Using TCPVIEW, from SysInternals, I can see that there's a process 
> called "system", with pid 8, which is having my port 99 opened.
> 
> Have you ever faced such situation ? I'm about to boot the server but I 
> think this is a pitty because everything else is working fine there.
> 
> thanXs in advance for your suPPort !

Jose Adriano Baltieri wrote:

> Well, I guess I've found a possible cause for this problem : a trojan horse.
>
> Running anti-virus on my server, it found a Windows DLL infected with it.

Ooooops!

So IMHO you need to install your server again from scratch... you don't
know what other gimmicks where installed through that backdoor. If the
trojan programmer knew what he was doing, you may not even own your server
anymore 

regards
Thomas Braun

web: www.software-braun.de / email: nospam@wegasoft.de
If you need to send email, substitute "nospam" with my initials
since the spam account is not checked on a regular basis.
Xbase++ FAQ : http://faq.xbasecentral.net