DescentBB

Why would I suddenly get this in D3 when connecting to a game? Any server. I get into D3, choose a pilot, and then this message, and dumps me to the main menu.

Only thing I did to the machine is install .NET on it. I don't recall if I saw this error before or after the install, though.

Network is fine for everything else.

Try the -useip command line option (or if it is already in your command line try removing it).

No go.

I checked the registry and the default connection was set to HEAT..know what, I forgot, I installed d3 fresh so I could get the single player mission set back on the disk...

I launched d3 manually and clicked on Multiplayer, then chose TCPIP, and set as default connection, then OK, and I got the same error message. I exited and checked the registry, the correct value is now there, so I went back in and tried again, same error.

I looked in the Descent3\\online folder, and teh TCPIPfile is named Direct TCP~IP.d3c, is this correct? I don't recall. It's the only one listed, as I was tired of clicking the wrong one and ending up waiting for a timeout, so I deleted the others.

Launching through Vortex, if Server Proxy is enabled and you have -useport 2092 it will do just that!

This message is shown when descent fails to initialize the UDP listening socket for port 2092.

The most obvious problem is, that some other application is still listening to that port.

run \"netstat -a\" on a console, and look for \"UDP LISTENING\" ports.

Bubba, you mean in Vortex's Settings -> Proxy? That's not checked, and I don't have the useport parameter.

Munk, netstat shows nothing for tcp on 2092, and for udp, it displays UDP metalliclient:2092 *:*

UDP is the relevant part here.

So now you have to figure out which application is blocking this port.
I know that TinyFirewall can show which application uses which port for listening, maybe there is some tool out there.

Use netstat -oa to figure out what app has already bound itself to UDP 2092. It'll give you a PID which you can look up in Task Manager.

TCPView may come handy.

The -oa did it...svchost was taking it, dunno what that was.

Thanks!

░

I know what it is, I just don't know what it was hosting.

Something new.. \"Tasklist /SVC\" will give you the PID and program names. Very cool.

Yeah, 'Tasklist /svc' is handy, but there is something else that is even more handy to use with it.

'tasklist /svc > tasklist.txt' > 'notepad tasklist.txt'

No more scrolling in command prompt windows.

Any command you enter into command prompt you can get the output to write to a file on the disk. Simply put ' > filename.txt' on the end of the command. For instance if you want to list all the hidden files in a directory and subdirectories, sorted by name then date then size grouping directories first, type 'dir /a:h /s /o:gnds > dirlist.txt' then when it is done, open that text document in notepad.

Interesting, I don't know why svchost would be watching that port.

I typically get that error when I launch D3 to join a game, and forget that I'm already running a D3 dedi server on that machine (which I often do when I'm not playing/working on it).

That's why you should not use 2092 for a dedi server. I use 2093+ for dedicated servers.

Grendel wrote:That's why you should not use 2092 for a dedi server. I use 2093+ for dedicated servers.

ZACTLY@@@@ 2092 should be used for your gaming machine

Ah, but I host a server on my gaming rig, when I'm not actively using it.

However, you're right, I could just as easily set the server to use port 2093 and avoid the conflict.

Krom wrote:Any command you enter into command prompt you can get the output to write to a file on the disk. Simply put ' > filename.txt'

Or you can use the pipe, and pipe the ouput to more. I wish Windows had an equivalent of less, which lets you scroll arbitrarily backwards and forwards, but anyway:
Will pipe the output to more without chewing up a file. Windows takes a few cues from the Unix world here.

If you have the .NET Framework 2.0 installed, you can get the Monad shell (or whatever they renamed it when it came out of beta). It's written in C# and is about as powerful as bash or tcsh on Unix, as you can write shell scripts in C# (called "cmdlets") and use them like uber-powerful batch files, without compiling them.