Thread title says it all; ASX simply didn't connect when I booted today. AFter going thru all the files, I found that my internal IP had changed! Consequently, my ASX network config files were all wrong!Has this happened to any of you, and what caused it?RhettFS box: E8500 (@ 3.80 ghz), AC Freezer 7 Pro, ASUS P5E3 Premium, BFG 8800GTX 756 (nVidia 169 WHQL), 4gb DDR3 1600 Patriot Cas7 7-7-7-20 (2T), PC Power 750, WD 150gb 10000rpm Raptor, Seagate 500gb, Silverstone TJ09 case, Vista Ultimate 64ASX Client: AMD 3700+ (@ 2.6 ghz), 7800GT

I don't mess with DHCP for this very reason. I use all fixed and assigned TCP/IP addresses on my side of the router. Cable and other high speed internet providers require you to use DHCP when going out to their servers partly as a security procedure but also as a control issue, and you have just discovered the downside for the user with that policy. It shouldn't happen all that often but it can and probably will happen again. If you have only the one computer fixed IP addresses are probably not an option for you so just be aware that it could happen again.Call your internet provider and discuss it with them, too.

>I don't mess with DHCP for this very reason. I use all fixed>and assigned TCP/IP addresses on my side of the router. >At work, our network's internal IP's never change, unless *I* change them. So how could this happen at my house?That's what I don't understand. External, dynamic IP's I can understand, but internals? I don't get that.RhettFS box: E8500 (@ 3.80 ghz), AC Freezer 7 Pro, ASUS P5E3 Premium, BFG 8800GTX 756 (nVidia 169 WHQL), 4gb DDR3 1600 Patriot Cas7 7-7-7-20 (2T), PC Power 750, WD 150gb 10000rpm Raptor, Seagate 500gb, Silverstone TJ09 case, Vista Ultimate 64ASX Client: AMD 3700+ (@ 2.6 ghz), 7800GT

That's what the D in DHCP stands for: Dynamic. It can change whenever it "feels" like it, unless you lock the addresses down. Just because it's never happened before doesn't mean it never will -- at your house, or at work.I've never worked anywhere where the internal IP addresses weren't fixed and assigned. For this very reason. Hope this helps.

Hi,Did you reset your router to default settings?Did you have any power outage which may have triggered a reset?Jimhttp://www.hifisim.com/banners/hifi-community-sigbanner.jpghttp://www.hifisim.com/

>Hi,>>Did you reset your router to default settings?>>Did you have any power outage which may have triggered a>reset?Hurricane Ike.I was out of power for about a day.Maybe that did it.RhettFS box: E8500 (@ 3.80 ghz), AC Freezer 7 Pro, ASUS P5E3 Premium, BFG 8800GTX 756 (nVidia 169 WHQL), 4gb DDR3 1600 Patriot Cas7 7-7-7-20 (2T), PC Power 750, WD 150gb 10000rpm Raptor, Seagate 500gb, Silverstone TJ09 case, Vista Ultimate 64ASX Client: AMD 3700+ (@ 2.6 ghz), 7800GT

>That's what the D in DHCP stands for: Dynamic. It can>change whenever it "feels" like it, unless you lock the>addresses down. How is this done? As you can probably tell, I am not a network guy at work, that's not my area of expertise, so......is it possible to ensure that my internal IP's are fixed? At work the internal IP's don't change, so they must have known how to make them static. I guess they don't use DHCP?RhettFS box: E8500 (@ 3.80 ghz), AC Freezer 7 Pro, ASUS P5E3 Premium, BFG 8800GTX 756 (nVidia 169 WHQL), 4gb DDR3 1600 Patriot Cas7 7-7-7-20 (2T), PC Power 750, WD 150gb 10000rpm Raptor, Seagate 500gb, Silverstone TJ09 case, Vista Ultimate 64ASX Client: AMD 3700+ (@ 2.6 ghz), 7800GT

>>I was out of power for about a day.>>Maybe that did it.Ya think? :-lol

Dude, I'm sorry. By your last post I thought you were implying that you WERE the network guy at work. No, there is really nothing you can do if DHCP is required by your ISP BUT fortunately, it is a rare event. I wouldn't spend too much time on it any more, especially if it;s not a recurring problem. Now that you know what to look for next time it's not even worth worrying about now.If I'd just been through Hurricane Ike I'd be surprised and grateful I had any internet at all.

Yes, because your router lost power and it's settings generated a new IP.Jimhttp://www.hifisim.com/banners/hifi-community-sigbanner.jpghttp://www.hifisim.com/

>>That's what the D in DHCP stands for: Dynamic. It can>>change whenever it "feels" like it, unless you lock the>>addresses down. >>How is this done? As you can probably tell, I am not a>network guy at work, that's not my area of expertise, so...>>...is it possible to ensure that my internal IP's are fixed? >At work the internal IP's don't change, so they must have>known how to make them static. I guess they don't use DHCP?How does DHCP work?http://www.cisl.ucar.edu/nets/presentation...-SCD/sld010.htmHow can you prevent unexpected IP changes?1) Set up your router to use a lease time of "Forever".2) Set up your network with static network addresses instead of relying on DHCP.

Well given that I am 400 miles inland, you wouldn't think Ike would come through here with 75 mph winds for 7 hours straight. But it did. I've never seen anything like that, and I've been observing weather for 25 years.usually all we get is a breezy rain from those.RhettFS box: E8500 (@ 3.80 ghz), AC Freezer 7 Pro, ASUS P5E3 Premium, BFG 8800GTX 756 (nVidia 169 WHQL), 4gb DDR3 1600 Patriot Cas7 7-7-7-20 (2T), PC Power 750, WD 150gb 10000rpm Raptor, Seagate 500gb, Silverstone TJ09 case, Vista Ultimate 64ASX Client: AMD 3700+ (@ 2.6 ghz), 7800GT

My Dad is part of Red Cross and just got back home. He was in Tyler(sp) and felt things pretty well also. Ike was one huge system.Jimhttp://www.hifisim.com/banners/hifi-community-sigbanner.jpghttp://www.hifisim.com/