Switched Coax to Cat5, receiver wont Connect

Message that displays after 5 - 10 mins after each reboot.

What you did should work so maybe there something wrong with that cat5 cable.  It was the only new thing you introduced.  Is there some way you can move the tv and that receiver closer to the gateway to test out another (and I assume shorter) known to be good cable?  Alternatively some other way to test that new cat5 cable?

I have rebooted the Gateway multiple ways and multiple times. I also rebooted the dvr, the basement and bedroom receivers and I still can't get the bedroom receiver to connect. All other tvs, computers, and receivers are working fine.  The bedroom receiver was working this morning, with coax. 

The only significant things that had to be rebooted were the gateway first (pull plug for 15 secs. and let it fully reboot) and after that the dvr (pull plug for 15 secs.).  Lastly would come the newly connected receiver.

Another alternate idea might be to exchange the ISB7000 for a wireless receiver (for example ISB7005) and get rid of the cat5 altogether.  Of course that assumes it's "close enough" to the WAP (wireless access point - small box ethernet connected to gateway) which you can't really know until you try it.

Cant move TV but could move receiver to basement TV and plug it in.  That won't cause any issues will it?  Im also going to double check my Cat5 I typically dont have cable issues, but you're right thats the only new item.

If you another already working cat5 connection to another receiver/tv I see no problem bringing the receiver down to there to test it out.  I would expect it will work.  And I would expect that if you bring that other "working" receiver it probably will not work on the new cat5 cable, i.e., same behavior you originally had.  That would prove it's the cable (connection) and not the receiver itself.

...or in less words, switch the two receivers around!

So it's definitely a cabling issue, however I'm confused on what that issue is...  I swapped receivers and it tested as expected.  But then i connected my laptop to the new cat 5 that I installed and I was able to get to the internet. (Yes, I turned WiFi off).  Is there a cabling distance on the Cat5 that I'm exceeding with the Uverse receiver?  Coax worked over the same distance so, I'm confused.

Disregard.  Its a physically bad cable.  Thanks for helping me think through everything.

Comparing distance requirements between coax and ethernet is like comparing apples and oranges.  But here's some things that come to mind about ethernet cables:

• Just how long an ethenet cable are you using?  It's length must be less than 100 meters (328 feet)?
• Is it really cat5 (10-100 Mbps) and not cat5e (1000Mbps)?   I think cat5 is "good enough" but I would feel safer with cat5e.
• T568A vs. T568B pin connections (not sure it really makes a difference)?

Otherwise, I don't know why your cable doesn't work to the receiver.

Update: I apparently was typing this reply while you created the previous post.  Ok, glad you found the problem.  FWIW, when it comes to cables (and connectors, and lost of other stuff) I always recommend monoprice.com.

Thanks for the website.  I have not used that website, but I just checked it out and it looks great.