Forum ‹ C# ‹ Problem with the New version of the development server

[QiX]

Hi,

I'm finally Downloaded and installed the new version of the dev pack.
I followed all the steps you mentioned, but when I try to run the server, i get an error saying the port is already in use.
I've checked, and there are no processes using this port, another version of the server isn't running.
and I've even set a rule in my windows firewall to allow all connections through port 8184.

once I've downgraded back to 1.6 version, everything started working well again.

any ideas?
Thanks in advance,

Meny

[Oliver]

Hey QiX,

If you kill all programs and then download the dev pack from our site, and just try to run one of the examples directly, does it still give the error?

- Oliver

[fox1980]

You can use "netstat" from the command line to check if some other application is using that port. Also, in your firewall settings check if that port is not bound to a specific application, updating the dev pack will result in a different signature for the file, so even if they are named the same the firewall might think they're not the same application.

[Oliver]

Fox,

Also, in your firewall settings check if that port is not bound to a specific application, updating the dev pack will result in a different signature for the file

That's interesting... Does it popup a new "allow this application" dialog then?

- Oliver

[fox1980]

That's interesting... Does it popup a new "allow this application" dialog then?

I don't know cause i have an hardware firewall so i always disable the OS one. If you wanna find out if the firewall is really the issue just disable it for a little while, test your application and then turn your firewall back up.

[QiX]

Hmm.. Hi Again.

Well I gave the upgrade another shot now.
I'm still facing the same problem.

It's still saying the port 8184 is in use.
I've turned off the OS firewall, and can't see anything in netstat about this port:

Proto Local Address Foreign Address State
TCP 127.0.0.1:61856 activate:61857 ESTABLISHED
TCP 127.0.0.1:61857 activate:61856 ESTABLISHED
TCP 192.168.1.101:2869 192.168.1.1:34756 TIME_WAIT
TCP 192.168.1.101:61828 app54:https ESTABLISHED
TCP 192.168.1.101:61847 by2msg4020109:msnp ESTABLISHED
TCP 192.168.1.101:62642 95.35.244.102:9619 ESTABLISHED
TCP 192.168.1.101:63165 77.66.63.117:http ESTABLISHED
TCP 192.168.1.101:63193 77.66.63.117:http ESTABLISHED
TCP 192.168.1.101:63274 fx-in-f109:pop3s ESTABLISHED


Got any other ideas maybe?
and Oliver, as far as I remember, the OS firewall does ask if you allow this connection to be made if it doesn't recognize it.

Thanks again,
QiX

[Benjaminsen]

Quick question, what operative system are you running? Something strange like XP64 bit or so?

[QiX]

Win 7, 32Bit

[Benjaminsen]

Did you disable IP v6?

[Oliver]

Or did you disable ipv4 ?

[QiX]

I haven't disabled neither of them (should I??)

just to point out again, once i Downgrade back to ver 1.6 everything is working fine

[Oliver]

You shouldn't disable them, at least not for our sake.

Try the attached build, it might be better...

[QiX]

Same problem still :/

I'm either doing something really really wrong, or my laptop is messed up.
I don't think it has anything to do with your build (didn't see any other complaints)

QiX

[fox1980]

All the builds i tried worked fine for me, and i'm also using Win7 32bit. Laptops usually come loaded with software, maybe you got something in there that is blocking that port. An antispyware, or antivirus maybe.
Also you could try to disable UAC just to make sure it's not a permission error.

[QiX]

Hi Fox,

I don't think its a port issue because it works fine when I use build v1.6.
only things running in the background are the Windows Firewall and the Node32 AV i got.
I'm pretty sure that if one of them was the problematic one, i'd have the same issue with the new build.
This thing is really driving me insane :S

at least I'm able to debug and do all the other things with v1.6

QiX

[QiX]

oh and UAC is disabled since I got Win 7 (Thats a nasty and annoying feature!)


QiX

[jak322]

Just for everyone's info I have the same issue but I get around it by loading the server twice and then closing the first one which displays the "Are you connected to the internet" message. I'm also on Win7 32b.

James