Todd#43

gabbais

gabbai

Hmmm....must have had another internet argument go a little too far. Someone's GOT to know the story here....

Eh....you're young - you'll get over it. Everyone else? Fuck 'em - they'll either adjust, get over it, or leave. Either way, you win. You figured out what happened, and more or less fixed it. That's a good day in my book.

Checks? WTF?? People still use those? Don't mind me, I'm just trying to boost my post count back to where it was before the shit hit the fan. Carry on......

Who cares??? We should be so lucky. Sorry to Jack the thread. Thanks for the work you do. If anyone is worried about the mindless drivel they lost, I've got two words - fuck off. You really should take a hard line approach, there Ben. I mean your name is SATAN afterall....

gabby

Fuck...I had 18 this morning. Now I have 3? I didn't even post anything yet.

Lots of things to check here. I'm assuming that you're checking the distance from the top of the fork tube (or cap) to the top of the upper triple, right? If you are, this distance really doesn't me shit relative to the geometry of the bike. For example, you could have one fork tube 3 feet longer than the other, and as long as the extra 3 feet was sticking out the top of the triple, your geometry is fine. What you should check is the distance from the top of the lower triple to the centerline of the front axle. This is a much more accurate representation of what is going on with the geometry. If its the same, its entirely possble that you twisted the tube while you were moving things up and down in the triples. No big deal. If those dimensions are the same, you're

Were they off before you dropped the front? If they weren't, your forks may have been twisted in the trees, and by loosening everything up you got the misalignment out. On the other hand, you may have twisted things up by dropping the forks. The only way to know for sure is to check it. The position of the compression or rebound screws dont really mean anything as far as the front end alignment goes. If they're different than they were before the adjustment means something has changed.

In case anyone is still wondering the computer is fixed. Seems the TCP and/or Winsock stacks were corrupt. I downloaded a "tool" and it worked fine with (so far) no ill effects. If anything pops up down the road, I'll let you know. Thanks to everyone who offered their suggestions!

The CAT5 Cable that I'm using now is fine - I used it with one of the known working computers. The port is also fine - It worked with one of the known good computers also. I reset the gateway days ago, and probably 50 times since then. I've unistalled and re-installed the adapter drivers so many times I'm surprised that I havent burnt up my USB port. I've heard of some tools that are supposed to rebuild the Winsock and TCP stacks - maybe I'll try one of them tonight.

All that's in there is 127.0.0.1 localhost - nothing else. Eh...I'll keep trying.

Continuing this discussion (since I haven't figured it out yet).... Does anyone know what should be in the "hosts" file?

Still nothing on this end.... I'm about to throw it in the garbage. Anyone want a lightly used Dell???

So, maybe Liz isn't such a bad guy after all?

The functioning computers use the 2Wire device as the DNS Server, and that's what I set the non-functioning computer to use.

The two computers that are currently connected are getting the DNS and IP automatically. The third computer will not obtain the DNS or the IP automatically, so I tried forcing them from the TCP/IP properties. When I did that I could finally connect to the router and the rest of my network, but not the internet. Yup, did that and it will connect to the gateway (router) and the rest of my network, but not to the internet. Right now I'm plugged right into the router. I think the HPNA is more for the IPTV than the regular computer stuff. One of the computers that is connected is wireless (802.11g) and the other is wired with a 10/100 Ethernet card. They work PERFECTLY I'll give that a try. If its too techy, I probably wont get it though.

I suppose I could call them again, but I'm doubtfull that its a uverse issue. The other computers in the house work fine.

I've had as many as four devices connected to the router with no issues other than this particular computer. Ive tried it wired and wireless and it doesnt work. I can force the IP (yes, one that's not being used by the other devices) and it will connect to the router and allow me access to my network (files and printers on other computers) but I can not get to the internet. Oh yeah...the router is a 2Wire 3800HGV.

Yup, everything else that connected to the router has no problem getting to the internet. Its just one computer that's having a problem. I've had plenty of problems back in the day with the Linksys products - routers and adapters. Haven't used them in years. The 2Wire products have been pretty bullet-proof for me. Used the last one for over three years with no issues. I'm getting everything I need from the router - the other two PC's that are connected have no problems. The hardware is brand new (well two weeks old) and the firmware in it is up to date. Again, two other computers are connected currently and run no problem. The network adapters that I've tried in the computer in question also function fine in other computers that connected to this gateway. I'm pretty sure that the hardware (gateway, adapters, cables) aren't the issue.

Let me know if you've got any ideas.

The dude who came out to do the install did a fantastic job. I've got no complaints - he was here about 8 hours. I watched him set up the other computers and since I've set up wireless before, I figured I wouldnt have any trouble with this one. It should be pretty easy. That being said, I've called Uverse tech support no less than 6 times. All they tell me is they dont support the computers or cards (unless I buy the card from them) so they can't fix it.