Networking equipment - not sure what happened

deathnote666

Note that I wasn't there in person and was remoted into one computer trying to remote into another.

The computer I was remoted into was on ethernet.

The target computer was connected to both ethernet and wireless.

I was only getting 1/4 packets back or less when I pinged the ethernet and wireless IP's of the target computer. Just enough for it to show it was online but not enough return to connect to it.

The wireless has a repeater, and I saw that the target computer was going through the repeater.

I rebooted the repeater and the target computer connected to the repeater again.

I was able to ping another computer through the repeater and connect to it just fine so nothing is wrong with the repeater. Pinging the target computer through the repeater had the same packet drop as pinging from the computer I was remoted into.

After a 2nd reboot of the repeater, the target computer didn't reconnect to the repeater or any other wireless.

At the same time, the ethernet IP of the target computer quit dropping packets, when pinging, and I was finally able to connect to it.

What exactly happened here?

Shadowfire

Strictly a guess: is the repeater running the same SSID/PW as the main network? Often repeaters doing this will cause all sorts of problems when devices can see both access points. Reason being that repeaters are just repeaters, they don't do any load balancing, and client devices just see a thing to connect to and go "ok" and can flake back and forth between multiple access points without realizing what's happening. On top of that, you have a wired connection there and everything together was probably creating a switching loop, and with a flaky repeater I wouldn't doubt a broadcast storm being the cause of your problems.

deathnote666

Shadowfire wrote: »

Strictly a guess: is the repeater running the same SSID/PW as the main network? Often repeaters doing this will cause all sorts of problems when devices can see both access points. Reason being that repeaters are just repeaters, they don't do any load balancing, and client devices just see a thing to connect to and go "ok" and can flake back and forth between multiple access points without realizing what's happening. On top of that, you have a wired connection there and everything together was probably creating a switching loop, and with a flaky repeater I wouldn't doubt a broadcast storm being the cause of your problems.

I've never had an issue with having wireless/wired connection at the same time before.

Switched it to the main wireless and the issue resumed. No idea when the issue started again so it could be a coincidence or it can't handle both. Was originally connected to both because there were claims of wired issues.

Was able to kick the computer off of the wireless again and the issue remains...

The main wireless does have spanning tree protocol.

The repeater has a different SSID.