Digital Paint Discussion Board

Paintball 2: The Game => Server Discussion => Topic started by: MrLuke on January 04, 2008, 05:46:18 AM

Title: Server Sending Internal Ip instead
Post by: MrLuke on January 04, 2008, 05:46:18 AM
My Sevrer is ONLY sending out an internal ip adress which otheres cannot connect to.
Server set to public
Im using a router.
Ports are forwarded to 27910
static ip adress: 192.168.1.136
Firewall off and allowed (unless avg has firewall i dont no about)

my server sends a heart beat eventhough its an internal ip address.

the sever appears only in my paintball server list in the game. it connects to 192.168.1.136. It does NOT show up in sevrer browser.

.............................................................
DP Resource Public Server Troubleshooter
Specified server information: 220.245.178.134:27910
RCON password provided? yes
Run at Fri, 04 Jan 2008 10:45:18 +0000

TEST PROCESS
===================
> Checking if 220.245.178.134: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




Title: Re: Server Sending Internal Ip instead
Post by: Cameron on January 04, 2008, 05:54:11 AM
Yeh, that same thing is happening to me as well.  When i updated to build 20 my server worked once then when i killed the console and started it up the next day it wouldn't do anything.  I found it had also changed the port somehow, forwarded the new port and it still doesn't work. I see the server in the "join game" section (obvious) and on the serverlist.php thing but i get exactly the same thing as MrLuke.
Title: Re: Server Sending Internal Ip instead
Post by: KnacK on January 04, 2008, 06:59:19 AM
1. Make sure that your public ip, 220.245.178.134, is forwarded to your pivate ip, 192.168.1.136.
2. Make sure ports 27910-27910 UDP is forwarded from public ip to private ip.
3. Post a screenshot of your port forwarding page from your router so that we can review it.
4. Make sur eWIndows Firewall is either off or has these ports opened up.
Title: Re: Server Sending Internal Ip instead
Post by: FlaMe on January 04, 2008, 07:03:17 AM
AVG probabaly does have a firewall or your ports are not forwarded.
Title: Re: Server Sending Internal Ip instead
Post by: Cameron on January 04, 2008, 07:05:36 AM
Hmm...  Dont work 4 me, i'll post a screenshot when i get on the other computer.
Title: Re: Server Sending Internal Ip instead
Post by: Zorchenhimer on January 04, 2008, 04:43:12 PM
Firewall off and allowed (unless avg has firewall i dont no about)

What version do you have? The free one?  If so then there is no firewall included.
Title: Re: Server Sending Internal Ip instead
Post by: KiLo on January 04, 2008, 05:18:33 PM
Try typing setmaster dplogin.com directly into the console.
Title: Re: Server Sending Internal Ip instead
Post by: MrLuke on January 05, 2008, 12:26:08 AM
I am using the avg free edition
and when i type setmaster dplogin.com  into console it says "only public dedicated severs use masters"
How do i foward public ip, 220.245.178.135, to my pivate ip, 192.168.1.136 ?
Title: Re: Server Sending Internal Ip instead
Post by: Cameron on January 05, 2008, 01:39:16 AM
fixed mine. after all of the restarts of my router due to mIRC i found the internal ip of the computer had changed and worked perfectly.  i wouldn't suggest it but restarting the router does fix some things such as that.
Title: Re: Server Sending Internal Ip instead
Post by: KiLo on January 05, 2008, 02:08:41 AM
MrLuke it sounds like you are just hitting the Start New Game button to run your server.

Use this handy little guide to setup a "internet" server: http://digitalpaint.planetquake.gamespy.com/docs/server_guide_win32.html
Title: Re: Server Sending Internal Ip instead
Post by: Cameron on January 05, 2008, 02:15:01 AM
MrLuke it sounds like you are just hitting the Start New Game button to run your server.

Use this handy little guide to setup a "internet" server: http://digitalpaint.planetquake.gamespy.com/docs/server_guide_win32.html
But if he is actually seeing all of that information he is most likely using the cmd console to run it.
Title: Re: Server Sending Internal Ip instead
Post by: Zorchenhimer on January 05, 2008, 02:18:30 AM
MrLuke it sounds like you are just hitting the Start New Game button to run your server.

Use this handy little guide to setup a "internet" server: http://digitalpaint.planetquake.gamespy.com/docs/server_guide_win32.html

Thats the problem.

Also, AVG free does not include the firewall.
Title: Re: Server Sending Internal Ip instead
Post by: KiLo on January 05, 2008, 02:21:13 AM
No. One line tells me that he is using that button.

Quote from: MrLuke
"only public dedicated severs use masters"

Edit: This was in response to Cameron.
Title: Re: Server Sending Internal Ip instead
Post by: Cameron on January 05, 2008, 02:45:19 AM
O yeah, i remember getting that when i used the Start New Game.  My Apologies.
Title: Re: Server Sending Internal Ip instead
Post by: MrLuke on January 05, 2008, 03:21:07 AM
MrLuke it sounds like you are just hitting the Start New Game button to run your server.

Nope!!!! i have set it up correctly using the shorcut to paintball & changed the target to "C:\Games\Paintball Server\paintball2.exe" +set dedicated 1 +set public 1 +exec myserver.cfg +map propaint1.
i
 have set a server up on a computer from a another house which worked. but  i cant find the fault with this one
Title: Re: Server Sending Internal Ip instead
Post by: KnacK on January 05, 2008, 08:50:28 AM
you need to port forward 27900 from your public ip to your server so that others can see your server.

Also, in your command line startup, you need to add " +set public 1" so that it is a public server.
Title: Re: Server Sending Internal Ip instead
Post by: Cameron on January 05, 2008, 04:35:10 PM
you need to port forward 27900 from your public ip to your server so that others can see your server.
Wow, never knew that.  Now i dont have to hand out the i.p address anymore.
Title: Re: Server Sending Internal Ip instead
Post by: MrLuke on January 07, 2008, 03:21:27 AM
ok i have forward 27900 to 220.245.178.135
already had +set public 1 in my command line
still not working.  any other suggestions?
Title: Re: Server Sending Internal Ip instead
Post by: KiLo on January 07, 2008, 03:22:14 AM
The default port is 27910 forward that.

Make sure that you are forwarding on UDP too.
Title: Re: Server Sending Internal Ip instead
Post by: MrLuke on January 07, 2008, 11:52:37 PM
Still not working. How does that look?
Title: Re: Server Sending Internal Ip instead
Post by: KnacK on January 08, 2008, 06:55:16 AM
27900 needs to be forwarded to 192.168.1.136 just like 27910.
Title: Re: Server Sending Internal Ip instead
Post by: KiLo on January 08, 2008, 08: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.
Title: Re: Server Sending Internal Ip instead
Post by: KnacK on January 08, 2008, 09: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.
Title: Re: Server Sending Internal Ip instead
Post by: Cameron on January 08, 2008, 07: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.
Title: Re: Server Sending Internal Ip instead
Post by: KnacK on January 08, 2008, 07: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.
Title: Re: Server Sending Internal Ip instead
Post by: MrLuke on January 09, 2008, 06: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?
Title: Re: Server Sending Internal Ip instead
Post by: KnacK on January 09, 2008, 06: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?
Title: Re: Server Sending Internal Ip instead
Post by: MrLuke on January 09, 2008, 06: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




Title: Re: Server Sending Internal Ip instead
Post by: MrLuke on January 09, 2008, 07: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?

Title: Re: Server Sending Internal Ip instead
Post by: MrLuke on January 09, 2008, 08: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
Title: Re: Server Sending Internal Ip instead
Post by: KnacK on January 09, 2008, 08: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
Title: Re: Server Sending Internal Ip instead
Post by: MrLuke on January 09, 2008, 08:06:18 AM
ip chicken adress is 220.245.178.131
last time i checked this it was
220.245.178.135
Title: Re: Server Sending Internal Ip instead
Post by: KiLo on January 09, 2008, 03:11:23 PM
When you get to the screen below try typing: setmaster dplogin.com

(http://i201.photobucket.com/albums/aa85/mjet214/luke_cmnd.jpg)
Title: Re: Server Sending Internal Ip instead
Post by: FlaMe on January 09, 2008, 04: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
Title: Re: Server Sending Internal Ip instead
Post by: MrLuke on January 10, 2008, 01:43:07 AM
well every1 but me can see it so im happy with that
thanks for all the help