Page 1 of 1

Problem connecting behind router.

Posted: Tue Jun 06, 2006 5:31 am
by Bitplane
Hello all,

first post here: I would like to thank Koolbear for the service and Zico for once again bringing my neighbors to the point of insanity (hey I cannot re-play Descent 1 without sound volume at max level :p).

'Slight problem with a mirror'?

Let me explain shortly how things are setup here:
Modem: Wanadoo (Netherlands) Livebox. That is ADSL with a router in it. Splits VOIP and Ethernet, can jack 2 PC's into it.
It has my IP # but gives 192.168.1.10 to my first PC, and 192.168.1.11 to second local.
So - in that setup, I can play on my LAN.
And if I connect to someone else's server, with a direct IP number, that works too.
But if I setup a server, it will not work. I can give someone my IP addy, but he will not be able to 'get through'.
Now I figured I should tell my nice router/modem to Forward a Port (that is about as far as my knowledge goes in these matter I am sorry to have to admit).
So I gave it 5100 (because I had no clue if the 'socket 5100h' talked about in hmm I think it was my original 1.4 release notes? - meant it *was* 5100 *in* hex or if it should be decimalized ;) ) and also put a FW on 20736 (dec value of 5100).
No go.

Values I have entered in my Firewall settings for that Livebox Modem are:

Name (just a label)
Access activated yes
Protocol udp*
* that is what I select in Multiplayer
Port from 5100**
** also have one identical set but with 20736
Port to

Posted: Tue Jun 06, 2006 5:45 am
by CDN_Merlin
Are you giving your friend the 192.168.x.x IP or the one given from your ISP? Also, you should use kali to play D1/2.

www.kali.net

Update

Posted: Tue Jun 06, 2006 6:53 am
by Bitplane
Hi Merlin,

hmm Kali - I would like to try without it, but I will definitely look up what it does and does not do, quite likely download later.

I give anyone who tries to connect my modem IP #, since 192.168 is local.

They get a 'connection time out' signal in D1.

Would you (or anyone) happen to know if that 5100h is indeed the PORT number?
I still have no clue on that ;).

Thanks for the advice! Please note my question comes in 2 parts (it got split up at some point).

Thanks,
Lucas aka Bitplane.

* I say, there is no
* darkness but ignorance.
-
* Twelfth-night; or, What You Will

Correction

Posted: Tue Jun 06, 2006 6:57 am
by Bitplane
Hmm that 'connection time out' seems odd.
What happens is it cannot do the handshake,and times out.

L/B

Posted: Tue Jun 06, 2006 8:34 am
by CDN_Merlin
What version of D1 are you running? Is it the new D1x type? There should be some documentation on what to open. You may also check windows firewall and see if it's blocking it.

Posted: Tue Jun 06, 2006 9:40 am
by fliptw
D1/D2 does not support Internet networking.

D2X XL does.

Answers...

Posted: Tue Jun 06, 2006 9:43 am
by Bitplane
Hi,

I am running D1 Rebirth - should have mentioned that ;).

I did mention (in part 2 of my question) that I do not have any other firewalls :).

Thanks for trying to help!

I still do not know what the port number is. Anyone?If it is not 5100h, that might very well be my problem.

Any and all suggestions appreciated,
Lucas aka Bitplane

* The fool doth think he is wise, but the
* wise man knows himself to be a fool.
-
* As You Like It

Posted: Tue Jun 06, 2006 10:58 am
by CDN_Merlin
The port won't have a letter in it if there is a port. Could be your modem/router just doesn't allow someone connecting from the outside.

Posted: Tue Jun 06, 2006 11:44 am
by BUBBALOU
KALI nuff said

you want your external Ip address um .. BOK BOK

Updates

Posted: Wed Jun 07, 2006 4:42 am
by Bitplane
Hello,

Hmm the official notes state 'socket 5100h'. That means 5100 hex(adecimal). Now obviously 5100h is not a hex value - hex is after all to 16, and that means 'F' is the highest letter ;).

What I did not know is whether the 5100 was 5100 'raw' or 20736 (dec of 5100; this seems logical). So I put 2 holes (forwards of a port) in my firewall. It does of course allow traffic; otherwise it would be sorta useless ;). I do have a teamspeak server running at a specific port. Anyone can get on it.

Alas, the problem remains. I do not know if 'socket' equals 'port' - I might still simply have the *wrong* number which would of course prevent a connection to be established.

Question: some of you mention Kali. Does Kali simply offer a solution to this? Anyone tried this with a router-firewall?

Oh and yes, I do give others my real IP addy, not the local one 8-).

Thanks for the help.
Lucas aka Bitplane