Server problem (FIXED)
- paintballkev812
- Posts: 210
- Joined: Tue Oct 04, 2005 12:25 am
Server problem (FIXED)
Well i found out a way to have others connect by adding "EXTERNALIP=71.114.187.36" in my system config file, but when i do i can't connect to my world by crashing into nor by using the "your world" shortcut. If i take out "EXTERNALIP=71.114.187.36" then i can connect, but no one else can (except marshall somehow got on once earlier today). Anyone know what to do?
Last edited by paintballkev812 on Sat Nov 12, 2005 2:44 pm, edited 2 times in total.
http://theuniversal.net/forum/viewtopic.php?t=3281
and >_>
Edit: Also, how are "others" connecting when you add external IP?
and >_>
Edit: Also, how are "others" connecting when you add external IP?
Last edited by theseer on Tue Nov 08, 2005 10:53 am, edited 1 time in total.
Sounds like your PC's on a LAN, or behind a NAT-ting firewall/router to me.
Here's my usual guess at a solution. Keep the external IP entry in your server config: without it, your world will be broadcasting an internal IP (eg 192.168.0.1, or something), which is why no-one else can connect but you can (because you're on that network). So, add the external entry, and everyone else can connect. Fine. Next you need to do a little jiggery-pokery to enable you to connect to your world too.
Add a file called reroute.txt to your clients/data folder. In it add a line like this:
a.b.c.d:eeee=127.0.0.1:eeee
where 'abcd' is your external IP address, and 'e' is the port your world is running on. If you're not specifying a port for your world you could try the same entry in rereoute.txt without the port, though I haven't ever tested that.
Anyway, save that text file; relog and see if it helps. It ought to means your client software will intercept all calls to your external IP and rereoute them back to itself.
f
Here's my usual guess at a solution. Keep the external IP entry in your server config: without it, your world will be broadcasting an internal IP (eg 192.168.0.1, or something), which is why no-one else can connect but you can (because you're on that network). So, add the external entry, and everyone else can connect. Fine. Next you need to do a little jiggery-pokery to enable you to connect to your world too.
Add a file called reroute.txt to your clients/data folder. In it add a line like this:
a.b.c.d:eeee=127.0.0.1:eeee
where 'abcd' is your external IP address, and 'e' is the port your world is running on. If you're not specifying a port for your world you could try the same entry in rereoute.txt without the port, though I haven't ever tested that.
Anyway, save that text file; relog and see if it helps. It ought to means your client software will intercept all calls to your external IP and rereoute them back to itself.
f
- Magicfinger
- Staff
- Posts: 1078
- Joined: Tue Sep 30, 2003 10:38 am
- Location: here,there and everywhere
- paintballkev812
- Posts: 210
- Joined: Tue Oct 04, 2005 12:25 am
Don't think i understand your question, but they just fly into the planet named Paint's Plazatheseer wrote:http://theuniversal.net/forum/viewtopic.php?t=3281
and >_>
Edit: Also, how are "others" connecting when you add external IP?
FINALLY IT WORKS
Last edited by paintballkev812 on Tue Nov 08, 2005 10:54 pm, edited 1 time in total.
adding an externalip=whatever line to the server config is needed on servers that are hosted on pc's that connect to the internet threw a router/hub/switch because without the line, the server will only look for clients connecting to the pc's network address and thus only allow clients to enterif they are in the network. with the externalip line added, the world will look for clients trying to connect on the real ip address.theseer wrote:Edit: Also, how are "others" connecting when you add external IP?
can see Guide to setting up your world on a routed network. for more detailed info on setting this up.
- paintballkev812
- Posts: 210
- Joined: Tue Oct 04, 2005 12:25 am