Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Wireless Connection keeps dropping


  • Please log in to reply

#16
susiegirl07

susiegirl07

    Member

  • Topic Starter
  • Member
  • PipPip
  • 49 posts
Let me change that last post. I am actually not disconnecting I am just stalling. My signal goes down to one bar and this page can't be displayed comes up until the signal gets stronger again.

Your help is greatly appreciated!!


Susie
  • 0

Advertisements


#17
Dan

Dan

    Trusted Tech

  • Retired Staff
  • 1,771 posts
Hi Susie,

Have there been any errors/warnings logged in your Event Viewer since you increased your TCP/IP limit to 100? (I'm not referring to the TCPIP error alone, I also want to know if there are any other errors.) If so, could you please post those errors/warnings.

Just out of curiosity, when your signal goes down to one bar, what happens when you run the ipconfig /release & /renew commands? Does your connection immediately return to full strength? Or does it remain at a low signal?

When your signal is very low, please do the following:
Goto Start --> Run --> type CMD and press OK --> now type: ping -n 100 192.168.1.1 and then press Enter. Wait for all of the pings to finish (there will be 100, so this could take a little while), and once it's done, please copy/paste the results into your next reply by right-clicking on the Command Prompt window, selecting 'Select All', pressing the Enter key, and then posting on this forum.

How far away is your router from your computer? Is there anything in between the two; ie: Walls?
  • 0

#18
susiegirl07

susiegirl07

    Member

  • Topic Starter
  • Member
  • PipPip
  • 49 posts
Hi,

I have not gotten any error messages lately expect for the ones I have already shown you. I did the ping 100 when the signal was low then it got strong again, then it disconnected. Here are the results:

Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Susan Cassells>ping -n 100 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time=12ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=11ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Hardware error.
Hardware error.
Hardware error.
Hardware error.
Hardware error.
Hardware error.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=9ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 100, Received = 48, Lost = 52 (52% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 12ms, Average = 5ms

C:\Documents and Settings\Susan Cassells>

Keeping in mind when it disconected it said hardware error. This card is only 3 months old if that with all updated drivers and software

Thank you so much for your help. :tazz:

Susie
  • 0

#19
susiegirl07

susiegirl07

    Member

  • Topic Starter
  • Member
  • PipPip
  • 49 posts
Here is the ping 100 when the signal was strong.
Thanks, Susie

C:\Documents and Settings\Susan Cassells>ping -n 100 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=9ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=53ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=9ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 53ms, Average = 6ms

C:\Documents and Settings\Susan Cassells>

Edited by susiegirl07, 09 March 2006 - 08:13 AM.

  • 0

#20
susiegirl07

susiegirl07

    Member

  • Topic Starter
  • Member
  • PipPip
  • 49 posts
This is the error message I get.

Event Type: Warning
Event Source: Dhcp
Event Category: None
Event ID: 1003
Date: 3/9/2006
Time: 9:50:09 AM
User: N/A
Computer: D9DFX941
Description:
Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 000CF166755B. The following error occurred:
The semaphore timeout period has expired. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.
Data:
0000: 79 00 00 00 y...

Thanks,
Susie
  • 0

#21
dsenette

dsenette

    Je suis Napoléon!

  • Administrator
  • 26,019 posts
  • MVP
your wireless card isn't getting an ip from the router for some reason...or at least it's not getting an ACK response from the router....hmmm...that does explain the trickle to a disconnect...(i think)...just don't know why it's doing this
  • 0

#22
susiegirl07

susiegirl07

    Member

  • Topic Starter
  • Member
  • PipPip
  • 49 posts
I don't either and it is driving me crazy!!!!!! Please let me know if here is anymore info that you need in order to fix this annoying problem. As I said before I have a Linksys WRT54GS Router with Verizon DSL. I am using WPA security on the router. I just switched from WEB but I was having this problem long before that.

My router is in my bedroom and the laptop is located in the next room. Even if I take i downstairs there is not much distance at all from it. Sometimes if I move the laptop to another position is will give me a stronger signal again. I have checked the network card and everything is fine with it as far as being connected.

Your help is GREATLY appreciated.

Thanks,
Susie

Edited by susiegirl07, 09 March 2006 - 10:50 AM.

  • 0

#23
dsenette

dsenette

    Je suis Napoléon!

  • Administrator
  • 26,019 posts
  • MVP
just to completely rule out interferance or obstructions...if your sitting next to the router...does this problem still occur? like..in the room on a chair next to the router
  • 0

#24
susiegirl07

susiegirl07

    Member

  • Topic Starter
  • Member
  • PipPip
  • 49 posts
Yes Icould be sitting right by the router and it will still happen.

Thank you,
Susie
  • 0

#25
rivekm

rivekm

    Member

  • Member
  • PipPip
  • 65 posts
Susie,

sorry i havent responded in some time- been busy. I noticed you have verizon and currently using dhcp...I would suggest changing from dhcp to ppoe, i am not sure this will solve it for you but verizon typically likes the ppoe. you will need all information from verizon, such as the number they provided you for your account access and stuff like that. Please try this and let me know, also, change the wpa first while doing this procedure and use wep and if all works then set up wpa again. Also, you might consider running the scan at the linksys website- it might suggest some issue it may be able to resolve. Also, when you set up the router initially you should do it hardwired, after settings are configured you change the ip address from 192.168.1.1 to wireless 192.168.2.1 you might even try that....that is how mine is configured and should be in the instructions with your wireless router. Let me know how it turns out
:tazz: :) :)
  • 0

Advertisements


#26
susiegirl07

susiegirl07

    Member

  • Topic Starter
  • Member
  • PipPip
  • 49 posts
I do have it set up as PPPOE, that is how verizon has to have it. I do have DHCP enabled on the router though....should that be disabled? I had it on WEP before and it I still had the same issues. When I set up the router it was hardwired, still is. My laptop is the one with the wireless connection that keeps dropping.

I don't understand what you are asking............change the router IP to wireless 192.168.2.1, what happens to the hard wire connection. Also where is there a scan on the linksys site.

Thanks for your help,
Susie

Edited by susiegirl07, 09 March 2006 - 04:14 PM.

  • 0

#27
rivekm

rivekm

    Member

  • Member
  • PipPip
  • 65 posts
yes on the router according to your post above, you are running dhcp. go into the router settings and change it from dhcp to ppoe, you will need your user id and password provided by verizon. and again, do you know what i mean about changing the ip from 192.168.1.1 to 2.1? Once you configure the router via hardwire, go into ip setting change to 2.1 and disconnect the rj45.
  • 0

#28
dsenette

dsenette

    Je suis Napoléon!

  • Administrator
  • 26,019 posts
  • MVP
rivekm, i personally don't see any posts where the user is showing the ROUTER as getting it's ip address from the ISP via dhcp....there are some ipconfigs from the COMPUTERS that are getting their ip via dhcp from the ROUTER...could you point out which post you're getting your info from? also...why change the router's ip from 1.1 to 2.1? that really won't make a difference
  • 0

#29
rivekm

rivekm

    Member

  • Member
  • PipPip
  • 65 posts
yes on the router according to your post above, you are running dhcp. go into the router settings and change it from dhcp to ppoe, you will need your user id and password provided by verizon. and again, do you know what i mean about changing the ip from 192.168.1.1 to 2.1? Once you configure the router via hardwire, go into ip setting change to 2.1 and disconnect the rj45.

never mind for now the ip addy change....
  • 0

#30
susiegirl07

susiegirl07

    Member

  • Topic Starter
  • Member
  • PipPip
  • 49 posts
My connection is set up for PPPOE. When I am on the basic setup page that is the first thing that is set. User name and password and the keep alive option. When you go down the page there is network setup and that is where the option for dhcp is enabled or disabled.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP