www.ClassicTW.com
http://www.classictw.com/

Wierd Error with Server
http://www.classictw.com/viewtopic.php?f=1&t=33624
Page 2 of 2

Author:  Oso [ Wed Dec 26, 2012 11:11 am ]
Post subject:  Re: Wierd Error with Server

No worries. We all have our blindspots when it comes to certain things.
It is always a good idea to have a static IP address for whatever PC you have hosting TWGS. That way you have one less thing that can break.
Check your router/firewall settings and see if you have port forwarding turned on for whatever port you have the game assigned to (23 or 2002, etc) and then make sure you have that IP address available. Sometimes another PC on your network will grab that address if it is available. If it is available, then change your PC's address to match. That should take care of the problem. Either way, you can set up a static IP address for your PC and then forward the needed ports to that IP address.

Author:  Samek15 [ Wed Dec 26, 2012 11:25 am ]
Post subject:  Re: Wierd Error with Server

ok so i went into my router settings and re-checked my port forwarding and when I fixed it to the current one listed. it fixed the problem, just dont know how to make it static so it won't change on me again :(

Author:  Micro [ Wed Dec 26, 2012 11:37 am ]
Post subject:  Re: Wierd Error with Server

Go into your network settings:

XP - start/control panel/network settings/local area connection
Vista or 7 - open network and sharing center/local area connection

Select properties, then Internet protocal version 4 (tcp/IPv4), then properties button.

Change the setting to "use the following IP address", and fill out all the fields.

Author:  Micro [ Wed Dec 26, 2012 11:39 am ]
Post subject:  Re: Wierd Error with Server

http://portforward.com/networking/static-xp.htm

Author:  Big D [ Wed Dec 26, 2012 2:06 pm ]
Post subject:  Re: Wierd Error with Server

Samek15 wrote:
ok so i went into my router settings and re-checked my port forwarding and when I fixed it to the current one listed. it fixed the problem, just dont know how to make it static so it won't change on me again :(


Your router will assign an internal IP to every device that connects to it. It will normailly reserve that LAN IP for each device, but if it is rebooted or power is lost, it will re-assign numbers and you may or may not get the same LAN IP. The best way to avoid this is to put your server as the DMZ host where your LAN IP will be the same as your WAN IP (World area network IP). This way when you lose power, the IP will always be updated correctly.
IP passthrough will work IF it has IPv4 capability. I've found that many of the new routers do not have that capability and you'll have the same issues as you do with port forwarding.

Author:  Mongoose [ Wed Dec 26, 2012 11:18 pm ]
Post subject:  Re: Wierd Error with Server

Another way to do it: Find out the MAC address of your server's network card and configure DHCP on the router to always assign a specific IP address to that MAC address. If you use this method, you could boot different operating systems and still get the same IP.

Author:  ElderProphet [ Thu Dec 27, 2012 9:59 pm ]
Post subject:  Re: Wierd Error with Server

Big D wrote:
The best way to avoid this is to put your server as the DMZ host where your LAN IP will be the same as your WAN IP (World area network IP). This way when you lose power, the IP will always be updated correctly.

Wow, that's chock-full of misinformation. This won't prevent your LAN IP from changing if it's assigned by DHCP. And if it changes, your DMZ forwarding will break too. DMZ *shouldn't* point to a PC. And WAN stands for Wide Area Network :P

Samek15, the steps I outlined *should* prevent it from happening again, and takes into account common router settings (and DHCP scopes). Making *certain* it doesn't happen again requires more familiarity with networking. If you want to tackle it, find out how to configure your router's DHCP scope to include a reservation, as Mongoose suggested. Then determine your MAC address using "ipconfig /all" - it's listed as the Physical Address.

Author:  Big D [ Thu Dec 27, 2012 10:14 pm ]
Post subject:  Re: Wierd Error with Server

ElderProphet wrote:
Big D wrote:
The best way to avoid this is to put your server as the DMZ host where your LAN IP will be the same as your WAN IP (World area network IP). This way when you lose power, the IP will always be updated correctly.

Wow, that's chock-full of misinformation. This won't prevent your LAN IP from changing if it's assigned by DHCP. And if it changes, your DMZ forwarding will break too. DMZ *shouldn't* point to a PC. And WAN stands for Wide Area Network :P

Samek15, the steps I outlined *should* prevent it from happening again, and takes into account common router settings (and DHCP scopes). Making *certain* it doesn't happen again requires more familiarity with networking. If you want to tackle it, find out how to configure your router's DHCP scope to include a reservation, as Mongoose suggested. Then determine your MAC address using "ipconfig /all" - it's listed as the Physical Address.


Your really don't know much about routers do you? If you put the server as the DMZ host, you won't be on the LAN. Your IP will be the exact same as the WAN is. It won't matter at that point because TWGS will only recognize the WAN IP. Sure, there's a greater chance that you can be hacked, but anytime your run a TWGS you are opening the server up for that. If you want to be secure, then you wouldn't be running a TWGS to start with.


a DMZ (sometimes referred to as a perimeter network) is a physical or logical subnetwork that contains and exposes an organization's external-facing services to a larger untrusted network, usually the Internet.

Author:  Comd Data [ Fri Dec 28, 2012 1:53 am ]
Post subject:  Re: Wierd Error with Server

http://portforward.com/ here is all the info you need sam.

Comd Data

Author:  Micro [ Fri Dec 28, 2012 9:27 am ]
Post subject:  Re: Wierd Error with Server

Big D wrote:
Your really don't know much about routers do you? If you put the server as the DMZ host, you won't be on the LAN. Your IP will be the exact same as the WAN is. It won't matter at that point because TWGS will only recognize the WAN IP. Sure, there's a greater chance that you can be hacked, but anytime your run a TWGS you are opening the server up for that. If you want to be secure, then you wouldn't be running a TWGS to start with.

That's not entirely accurate. In most consumer firewalls/routers, the DMZ is just forwarding all traffic from the WAN IP to an IP address on your LAN. Your computer still has an IP address on you LAN sub-net. Some of these consumer products may hide what they are actually doing to make it easier for a user to click DMZ and select any of the computers it has detected on the LAN. Behind the scene it is automatically making sure the IP address of this computer doesn't change by reserving it in the DHCP server.

A consumer style DMZ is a very bad idea, as all ports are forwarded to this IP, and you only need to open a couple ports for TWGS. You may as well throw the firewall/router away and connect the computer directly to the modem.


In most commercial firewalls, a DMZ is a separate sub-net i.e.:

WAN 98.174.20.128/28
DMZ 192.168.2.1/24
LAN 192.168.1.1/24

All of the computers on the LAN can access computers in the DMZ, but the computers in the DMZ can't access the LAN. Alternately, DMZ computers can be given real internet IP addresses, but they are still protected by the firewall.

Author:  Big D [ Fri Dec 28, 2012 1:00 pm ]
Post subject:  Re: Wierd Error with Server

Micro wrote:
That's not entirely accurate. In most consumer firewalls/routers, the DMZ is just forwarding all traffic from the WAN IP to an IP address on your LAN. Your computer still has an IP address on you LAN sub-net. Some of these consumer products may hide what they are actually doing to make it easier for a user to click DMZ and select any of the computers it has detected on the LAN. Behind the scene it is automatically making sure the IP address of this computer doesn't change by reserving it in the DHCP server.

A consumer style DMZ is a very bad idea, as all ports are forwarded to this IP, and you only need to open a couple ports for TWGS. You may as well throw the firewall/router away and connect the computer directly to the modem.


In most commercial firewalls, a DMZ is a separate sub-net i.e.:

WAN 98.174.20.128/28
DMZ 192.168.2.1/24
LAN 192.168.1.1/24

All of the computers on the LAN can access computers in the DMZ, but the computers in the DMZ can't access the LAN. Alternately, DMZ computers can be given real internet IP addresses, but they are still protected by the firewall.


I can't argue with most of this except the part below.

Micro wrote:
A consumer style DMZ is a very bad idea, as all ports are forwarded to this IP, and you only need to open a couple ports for TWGS. You may as well throw the firewall/router away and connect the computer directly to the modem.


It's not like you are throwing the router away because you still have the router to provide the rest of the units on the LAN. The firewall on routers are pretty much crap anyway. If you truly want to be safe then you wouldn't be allowing TWGS or many other programs on your network. Any IM is subject to security breeches, and even surfing the internet can create security problems. It's best to have each server set up to plug these security holes instead of depending on a router firewall to do it for you.
When you do have a pc in DMZ the TWGS will read ONLY the WAN IP and you never have to worry about it reading the LAN IP.
Granted, if you don't know how to protect your server, it may very well be a bad idea to put it in DMZ.

Author:  Samek15 [ Thu Jan 03, 2013 5:57 pm ]
Post subject:  Re: Wierd Error with Server

well either way guys, thanks for your help!!! :D HAPPY NEW YEAR!

Author:  Oso [ Thu Jan 03, 2013 6:55 pm ]
Post subject:  Re: Wierd Error with Server

Samek15 wrote:
well either way guys, thanks for your help!!! :D HAPPY NEW YEAR!


I'm glad you were able to take care of the problem, and Happy New Year to you too.

Page 2 of 2 All times are UTC - 5 hours
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group
http://www.phpbb.com/