Some of you know / guessed, I'm trying to set up a new server on 2k8 OS. I've done 2000, and 2k3... and my main goal is getting a working Clan system, and using IIS, as well as seeing (first hand) how the UAC interaction plays out.
My initial setup is 2k8 x86 (32-bit).
Now, I have the files in place, the DB set up and even a working ODBC connection. (I presume. I can access the DB via ODBC, but I can't prove the server using it.)
When I try to log in from a client, the client succeeds in making a connection to the server system, (host machine) 1 packet is logged by the PT server app, (the server program, not the host machine) but by monitoring TCP/IP stack on the server, I see that the connection is actually with the [system] process, not the PT Server executable.
The client then says "Connection failed" and any other attempt to connect with it, or any other client usually crashes the client.
The server opens a "TIME_WAIT" connection on 10009 to the [system] process for each client connection attempt, the last of these will be closed when I kill the server, but the only way to get rid of them all so that I can try again seems to be to reboot the server.
Additionally, the [system] process on my client PC holds those "TIME_WAIT" connections open so long as both systems are running.
I've not seen this on any other system, and it's not an issue I was expecting to encounter on Svr2k8. Window Firewall hasn't changed much since 2k3, this appears to be nothing to do with UAC, and again DEP hasn't changed that much since 2k3.
The one thing I can think of, is that I never ran IIS on 2k or 2k3, so it's possible that there is some base internet filtering going on in the IIS service, which might show up under the "[system]" process, because it is an NT core service, not a separate process in it's own right.
I've tried the IPFilt settings on the TCP/IP protocol of the servers NIC... I can block everything there, but no amount of expressly allowed port 10009 on TCP / UDP will allow it to bypass this [system] process. I've made sure there is an exception to allow port 10009, and / or to my PT server executable. Again, I can block communications to it that way, but can't bypass the packets getting stuck in this [system] process.
Anybody else seen this and have an answer, or any pointers?
This could be the "same issue" as the recent spate of "Connection failed" help requests, but I hope this one has some real information behind it. eg. I know the packets are being sent to the right IP, that the server app is getting the first one, but nothing after that, and that the OS is holding the connection open (tying up port 10009) even after the server app and client are closed, etc.
For the information of others:-
Spoiler:
