Topic: @Home switch - static > dynamic

[y]

We've lost our static ip! How can the external net config on the server be changed?

[Quade]

I've gone through this whole thing myself. My ISP refuses now to give out static IPs.

You can set up e-smith to pull a dynamic IP from the configuration panel, and more than likely your dynamic IP will be routable from the Internet. Then update your DNS to point to the new IP.

Unfortunately, as with all dynamic IPs, your address lease will expire--probably after a month if you're using Comcast, despite what their tech support says. However, you can use a dynamic-dns system, like dyndns.org, or easyDNS.com (my personal favorite, and this is what I use) and e-smith will update to this DNS for you anytime your IP changes.

(well, there's no native support for easyDNS, but there is a contributed HowTo and an RPM to add this--I *highly* recommend easyDNS over anything else)

Unfortunately, the @Home chageover hit the server-enthusiast community hard. In fact, you could say it hit close to @home... (sorry).

[erik de wild]

@home also changed my static IP for a dynamic IP. I was very surprised because the serviceman who installed the modem gave me te choice between static or dynamic. The strange thing is that my e-smith server was completely out of order and currupted. I had to use the linux tools for fixing the disk and the currupt file-system. At the end it worked again, but with a dynamic ip. My qusetion is:

can the change from static to dynamic while the server was running be the reason my server was mixed up, out of order and currupted.

with friendly regards,


erik de wild

[Quade]

Here's a problem that's really, really bothering me...

I had @Home, and now my ISP only offers dynamic IPs. My e-smith server (5.0) can connect just fine, and distribute IPs via DHCP. *But*, no one on the outside can access my server via the web or other services. However, they can ping the server with domain name or IP, and it resolves to the extremely long hostname assigned by my ISP (georgia13-adsl-22-55-66-33.ga.comcast.comcastonline.net, blah blah blah...)

It just seems like my server isn't responding, or perhaps my ISP is blocking those ports.

Here's the clincher...I can reset the modem, and allow my Windows XP machine to pull that dynamic IP. I have apache running on it anyway, and anyone can get to the website that I have running on it as long as I repoint my DNS (thanks, easyDNS!) to the new IP.

I can't, for the life of me, figure out why my Windoze machine can serve pages, while my E-Smith Linux box cannot.