05-19-2009, 04:21 AM
It appears you have set it up correctly for your LAN. In this case, you are setting a static IP to the clay PC, that is what you want. Your firewall needs to know where to forward the data. Do not confuse this w/ Static IP relative to the internet service provider (ISP).
You don't need no-ip for this. Your ISP, as most do, provide an IP, the public one. Sometimes it changes, sometimes it doesn't. No-Ip is a service that checks what your public IP address is. When it does that, it updates the No-IP service, and associates whatever DNS name you picked to now use the changed IP address.
Example Day 1 public IP is xx.xx.xx.25 No-IP DNS name is mysitesux.servegame.com
Example Day 10 public IP changed to xx.xx.xx.125 No-IP auto checks and updates the name mysitesux.servegame.com to recognize that.
So, if you were to do a ping from Dos prompt: ping mysitesux.servegame.com, it would resolve to xx.xx.xx.25 on Day 1, and then resolve to xx.xx.xx.125 on Day 10.
But this has nothing to do w/ you running a server.
I just noticed that your OP has a different public IP listed (ip:76.7.121.19) compared to your screenshots (67.232.80.22)
Your commandline startup -ip 192.168.1.74, is a LAN ip. I think you should change that to your public IP.....
You don't need no-ip for this. Your ISP, as most do, provide an IP, the public one. Sometimes it changes, sometimes it doesn't. No-Ip is a service that checks what your public IP address is. When it does that, it updates the No-IP service, and associates whatever DNS name you picked to now use the changed IP address.
Example Day 1 public IP is xx.xx.xx.25 No-IP DNS name is mysitesux.servegame.com
Example Day 10 public IP changed to xx.xx.xx.125 No-IP auto checks and updates the name mysitesux.servegame.com to recognize that.
So, if you were to do a ping from Dos prompt: ping mysitesux.servegame.com, it would resolve to xx.xx.xx.25 on Day 1, and then resolve to xx.xx.xx.125 on Day 10.
But this has nothing to do w/ you running a server.
I just noticed that your OP has a different public IP listed (ip:76.7.121.19) compared to your screenshots (67.232.80.22)
Your commandline startup -ip 192.168.1.74, is a LAN ip. I think you should change that to your public IP.....