Author Topic: Server Sending Internal Ip instead  (Read 5461 times)

KnacK

  • Global Moderator
  • Autococker
  • Posts: 3039
Re: Server Sending Internal Ip instead
« Reply #20 on: January 08, 2008, 05:55:16 AM »
27900 needs to be forwarded to 192.168.1.136 just like 27910.

KiLo

  • Autococker
  • Posts: 2086
Re: Server Sending Internal Ip instead
« Reply #21 on: January 08, 2008, 07:58:58 AM »
27900 needs to be forwarded to 192.168.1.136 just like 27910.

Why is he even forwarding 27900? I don't have 27900 forwarded on mine and it works just fine.

KnacK

  • Global Moderator
  • Autococker
  • Posts: 3039
Re: Server Sending Internal Ip instead
« Reply #22 on: January 08, 2008, 08:25:40 AM »
SOme routers with port forwarding are not statefull.  Meaning that if tcp or udp traffic generated from the internal network won't get out unless that port is open.

27900 is only needed if you want your server to show up on server lists.  27900 udp outbound is heartbeat traffic.

Cameron

  • Global Moderator
  • Autococker
  • Posts: 2686
Re: Server Sending Internal Ip instead
« Reply #23 on: January 08, 2008, 06:22:21 PM »
27900 is only needed if you want your server to show up on server lists.  27900 udp outbound is heartbeat traffic.
Hmm, not really.  Mine is viewable with 27910 only, don't need 27900.

KnacK

  • Global Moderator
  • Autococker
  • Posts: 3039
Re: Server Sending Internal Ip instead
« Reply #24 on: January 08, 2008, 06:24:48 PM »
Some routers with port forwardign are not stateful, not all.  In your case your port 27900 outbound udp doesnt have to be set up.

MrLuke

  • Stingray
  • Posts: 68
Re: Server Sending Internal Ip instead
« Reply #25 on: January 09, 2008, 05:42:02 AM »
ok the portforwarding looks like this now
27900 udp 192.168.1.136
27910 udp 192.168.1.136
and still not working
If there was a configuration in router settings to turn on/off access to creating servers what would it be or is there no such thing?

KnacK

  • Global Moderator
  • Autococker
  • Posts: 3039
Re: Server Sending Internal Ip instead
« Reply #26 on: January 09, 2008, 05:48:06 AM »
http://dplogin.com/forums/index.php?topic=9317.0

Check the server again and let me see the results.

ALso, when you start your server, are there any errors in teh comamnd box that stays open?

MrLuke

  • Stingray
  • Posts: 68
Re: Server Sending Internal Ip instead
« Reply #27 on: January 09, 2008, 05:57:28 AM »
DP Resource Public Server Troubleshooter
Specified server information: 220.245.178.141:27910
RCON password provided? yes
Run at Wed, 09 Jan 2008 11:56:56 +0000

TEST PROCESS
===================
> Checking if 220.245.178.141:27910 can be connected to...
>    Writing to socket: '\xFF\xFF\xFF\xFFstatus\n'
>    Attempting to read, 3 second timeout...
>    Error: ICMP destination unreachable: unreachable port
> Failed to connect to server!
> Checking server list...
> Getting server list from http://dplogin.com/serverlist.php
> No entries found on the server list

RECOMMENDATIONS
===================
* Your server may not even be running; try connecting to it on this computer: run /connect 127.0.0.1:27910 in console
* Your server's port may not be forwarded; make sure you forward your ports for UDP port 27910 (and make sure it's set to the right computer address)
* Your server's port may be firewalled; make sure you allow port 27910 through your firewall





MrLuke

  • Stingray
  • Posts: 68
Re: Server Sending Internal Ip instead
« Reply #28 on: January 09, 2008, 06:19:07 AM »
OK not even i can see my own server?
how did this guy connect?
which also means server is working?
yet i still connected to my sever from my internal ip?


MrLuke

  • Stingray
  • Posts: 68
Re: Server Sending Internal Ip instead
« Reply #29 on: January 09, 2008, 07:00:27 AM »
ok i found dizzle & got him to rejoin my sevrer n asked what my ip was.
he thinks it was 60.242.220.169:27910
where did this ip come from?
and why is my server in my server list as 192.168.1.136:27910?
but not in server browser

KnacK

  • Global Moderator
  • Autococker
  • Posts: 3039
Re: Server Sending Internal Ip instead
« Reply #30 on: January 09, 2008, 07:04:40 AM »
go to ipchicken.com and tell me what it says your ip is.

Other than that, it looks like everything is working as the heartbeat is being sent and acknowledged

MrLuke

  • Stingray
  • Posts: 68
Re: Server Sending Internal Ip instead
« Reply #31 on: January 09, 2008, 07:06:18 AM »
ip chicken adress is 220.245.178.131
last time i checked this it was
220.245.178.135

KiLo

  • Autococker
  • Posts: 2086
Re: Server Sending Internal Ip instead
« Reply #32 on: January 09, 2008, 02:11:23 PM »
When you get to the screen below try typing: setmaster dplogin.com


FlaMe

  • Autococker
  • Posts: 601
Re: Server Sending Internal Ip instead
« Reply #33 on: January 09, 2008, 03:59:55 PM »
sometimes it gets messed up based off the dynamicness (? is that a word) of his iP. i know some routers dont allow port forwarding unless u have a static

MrLuke

  • Stingray
  • Posts: 68
Re: Server Sending Internal Ip instead
« Reply #34 on: January 10, 2008, 12:43:07 AM »
well every1 but me can see it so im happy with that
thanks for all the help