Network Connection Problem

[POSTED TO alt.internet.wireless - REPLY ON USENET PLEASE]

Sounds like a DHCP configuration problem in the router, or a DHCP client issue in the PC. As a temporary fix, try manually configuring the PC for a non-conflicting static address.

That's amusing. We had a long thread some time back where I suggested the same and you were adamant that my suggestion (the above) was not a proper support fix.

Google is your friend.

:)

David.

[POSTED TO alt.internet.wireless - REPLY ON USENET PLEASE]

The key word there is "temporary". ( Did you miss that in your haste to respond? ;) To be clear, I meant that as troubleshooting only, to rule out other possible causes. I do lots of thing when troubleshooting that I would never dream of deploying in production. If that fixes the problem, then it's been isolated to DHCP, which should then be corrected and restored. Instead of being left as a fixed address, as you advocated.

It is indeed.

As I said, go back and Google because that's what I suggested at the time.

Yep, as suggested by me.

It wasn't you must have been using the wrong reading glasses perhaps?

:) (My work is done here)

David.

[POSTED TO alt.internet.wireless - REPLY ON USENET PLEASE]

The record speaks for itself.

Not really. But nice to see that you've come around.

Sorry, David, but no cigar.

Mine too.

Ammended post 4 hours later:

I put a hub in port 4 and connected the PC to the second hub and it worked well. This workaround is perplexing. Why woud this gateway drop a connection unless it is hooked to a hub? It worked well for years connected directly to the modem/router. ???????????? Any thoughts on this would really be appreciated. Gary

[POSTED TO alt.internet.wireless - REPLY ON USENET PLEASE]

Possible defective connector that gives intermittent results.

working fine. Things that make you go...........hmmmm.

On 6 Jun 2006 18:27:19 -0700, snipped-for-privacy@porterpcs.com wrote in :

working fine.

The defective connector could be in the router.

It does, I said (among plenty of other troubleshooting) during this thread

"Each of which takes far longer than the 30 seconds to just TRY note the key word here TRY bunging in an IP address, he has done that, we moved on, it seems like it was his bluetooth dongle. "

Which is what you dismissed at the time as poor troubleshooting yet you've now suggested exactly the same.

Too funny! :D

Quit spinning, you'll get dizzy.

David.

On Wed, 07 Jun 2006 19:20:09 GMT, David Taylor wrote in :

Indeed. As I wrote, selective quotation notwithstanding, the record speaks for itself.

I suggest you take your own advice.