Edit: Working now. Is Fatwallet.com down for everyone? Just me?

[Engineer]

Sorry to post but I'm curious if it's my home PC's or just FW being down.

Click me!


Anyone else or is it just me?

 

[helloedchen]

It's you.

 

[newb111]

It's not down, and hasn't been for those 3 days

 

[imported_weadjust]

Originally posted by: GideonX
It's you.

 

[Schfifty Five]

Try clearing your cookies or something.

 

[Engineer]

Damn. Must be my ISP or something (possibly router) because they're all (4 pc's in my house) down.

Damnit!!!

 

[Tooncesthedrivingcat]

No deals for you!!

 

[Engineer]

Originally posted by: Tooncesthedrivingcat
No deals for you!!

Nah, Slickdeals, the AT Hot Deals forum and the Hardforum Hot deals still work!

 

[woodie1]

I just got the site to load, something hosed up on your end.

 

[JujuFish]

Try: http://216.138.164.31/forums/hot-deals

 

[Engineer]

Originally posted by: JujuFish
Try: http://216.138.164.31/forums/hot-deals

Still doesn't work. However, I pinged www.fatwallet.com and it resolves to 216.138.164.39, not .31 as you listed. I'm using OpenDNS for my DNS. I still think it's my ISP.

Oh, and the ping works just fine.

 

[dudeman007]

http://downforeveryoneorjustme...t.com/forums/hot-deals

 

[Shawn]

Works for me. I prefer Slickdeals though.

 

[Engineer]

Originally posted by: dudeman007
http://downforeveryoneorjustme...t.com/forums/hot-deals

I :heart: you!

Well, I still don't have it working but the ATT DNS are quite a bit faster (or seem to be) than the OpenDNS servers.

 

[Zim Hosein]

You link works fine for me Engineer

 

[Engineer]

Originally posted by: Zim Hosein
You link works fine for me Engineer

Well, it started working for me about 3 minutes ago on this PC. I changed my router's DNS listings to ATT (from OpenDSN) and did an ipconfig /renew on the PC but it still didn't work. I was running an adware scan and tried FW again and it now works. I'll check out the upstairs PC in a moment.

Thanks all!

:beer: to Zim.

 

[slightlyhuman]

hmm sounds like a familiar problems i've had with ea.com

any kind of site with having to do with ea won't load for me. any idea? cmd pings is fine.

 

[RichardE]

Originally posted by: Engineer

Originally posted by: JujuFish
Try: http://216.138.164.31/forums/hot-deals

Still doesn't work. However, I pinged www.fatwallet.com and it resolves to 216.138.164.39, not .31 as you listed. I'm using OpenDNS for my DNS. I still think it's my ISP.

Oh, and the ping works just fine.

216.138.164.39 takes me to fatwallet.

 

[Zim Hosein]

Originally posted by: Engineer

Originally posted by: Zim Hosein
You link works fine for me Engineer

Well, it started working for me about 3 minutes ago on this PC. I changed my router's DNS listings to ATT (from OpenDSN) and did an ipconfig /renew on the PC but it still didn't work. I was running an adware scan and tried FW again and it now works. I'll check out the upstairs PC in a moment.

Thanks all!

:beer: to Zim.

I'm glad you got everything working

Thanks for the :beer:

Cheers Engineer! :beer:

 

[spidey07]

1) Power down your providers modem and any gear connected.
2) Wait at least one minute, 5 minutes would be better
3) Power up provider modem
4) Wait at least one minute, 2-3 is better
5) Power up any device connected to modem, wait at least one minute
6) Test with one device or eliminate any SOHO gear

Yes it sounds stupid, yes it solve most all problems, yes there are reasons why this solves most all problems - timers and state machines. You MUST reset them all.

 

[Eli]

Originally posted by: spidey07
1) Power down your providers modem and any gear connected.
2) Wait at least one minute, 5 minutes would be better
3) Power up provider modem
4) Wait at least one minute, 2-3 is better
5) Power up any device connected to modem, wait at least one minute
6) Test with one device or eliminate any SOHO gear

Yes it sounds stupid, yes it solve most all problems, yes there are reasons why this solves most all problems - timers and state machines. You MUST reset them all.

I've always been curious why waiting X amount of time before powering back up is better than just a fast reset.

Everything is being wiped from memory and such, what is the difference?

 

[JEDIYoda]

Originally posted by: Schfifty Five
Try clearing your cookies or something.

Windex is real good for cleaning cookies!!

 

[Engineer]

Originally posted by: spidey07
1) Power down your providers modem and any gear connected.
2) Wait at least one minute, 5 minutes would be better
3) Power up provider modem
4) Wait at least one minute, 2-3 is better
5) Power up any device connected to modem, wait at least one minute
6) Test with one device or eliminate any SOHO gear

Yes it sounds stupid, yes it solve most all problems, yes there are reasons why this solves most all problems - timers and state machines. You MUST reset them all.

I had actually done all of that (more than one time) in the last three days with no change. I don't know if the DNS change fixed it or whether timing was right for InsightBB and they fixed it. Everything is much smoother now also, so I assume since I didn't change anything else (other than DNS which had no immediate effect even upon IP refresh), that Insight found something and reset it.

 

[spidey07]

Originally posted by: Eli

Everything is being wiped from memory and such, what is the difference?

With networking there are state machines running at every OSI layer on every piece of equipment involved. In a steady state everything is good - but once there is a state change, especially at the physical layer and MAC layer things can get "not as expected".

Without getting into details communications/networking is meant to expect certain states. The transitions from every single piece of gear involved in this does it's best to follow standards.

Many times that just doesn't happen because software has bugs. By by waiting the times I described you FULLY CLEAR AND RESET all state machines not just on your own gear but many pieces of gear outside of your control.

Flipping thing on and off quickly is a bad thing in networking. It's not the memory, it is the state machines running and how every single piece interacts. Not to mention all the software running all these pieces.

 

[SoulAssassin]

Originally posted by: spidey07

Originally posted by: Eli

Everything is being wiped from memory and such, what is the difference?

With networking there are state machines running at every OSI layer on every piece of equipment involved. In a steady state everything is good - but once there is a state change, especially at the physical layer and MAC layer things can get "not as expected".

Without getting into details communications/networking is meant to expect certain states. The transitions from every single piece of gear involved in this does it's best to follow standards.

Many times that just doesn't happen because software has bugs. By by waiting the times I described you FULLY CLEAR AND RESET all state machines not just on your own gear but many pieces of gear outside of your control.

Flipping thing on and off quickly is a bad thing in networking. It's not the memory, it is the state machines running and how every single piece interacts. Not to mention all the software running all these pieces.

Or it just gives the capacitors time to power down.