

Wireless Router or really long cord?
#21
Posted 22 June 2012 - 10:29 PM
#22
Posted 22 June 2012 - 10:31 PM
#23
Posted 22 June 2012 - 10:33 PM
Beause it's one of the Frequenzies of Water...
Go up to the Attic and lay it over there. And as sayed 2x 50 Foot Cable no problem, just connect them with a RJC45 connector ( Which gives away about 30 Feet distanz but even so you are far below the 300 Feet maximum for good Wired Connection).
Wired have a reach without additional Powersource for 300 Foot.
#24
Posted 22 June 2012 - 10:35 PM
Elkarlo, on 22 June 2012 - 10:33 PM, said:
Beause it's one of the Frequenzies of Water...
Go up to the Attic and lay it over there. And as sayed 2x 50 Foot Cable no problem, just connect them with a RJC45 connector ( Which gives away about 30 Feet distanz but even so you are far below the 300 Feet maximum for good Wired Connection).
Wired have a reach without additional Powersource for 300 Foot.
why 2x50 when a 100 foot is cheaper?
http://www.newegg.co...N82E16812119318
#25
#26
Posted 22 June 2012 - 10:56 PM
http://www.newegg.co...line-Networking
#27
Posted 23 June 2012 - 01:03 PM
#28
Posted 23 June 2012 - 02:44 PM
50ft Cat-7.. (backwards compatibile) for $13.99 plus 4 bucks shipping, you can't touch this for that price in a retail store anywhere that I know of. I have ZERO degradation that I can see using this cable in my home network, I also run wireless N+ router with a built in 4 port Gigabit, switch sometimes when I feel Lazy for a round of 2 v 2 Supreme Commander (Forged Alliance) LAN party / beer fest, and yea I have a mini "DAS BOOT"..!!!! Using (high quality) N-1, and N+ wireless USB adapters (a couple of years old), I have 5 of those, and they work great as well.
#29
Posted 23 June 2012 - 06:28 PM
So I guess long story short WIRED
#30
Posted 23 June 2012 - 06:39 PM
In the real world, especially in your situation, OP, it doesn't matter what your internet setup is as some others have claimed; the reality is that regardless of your situation, going wireless will add 20-50ms of ping onto whatever you're already getting, and regardless of what other sources of latency there are in your situation, that added latency is just going to hurt things one way or the other. Getting a wire will be cheaper, and the results will be better.
#31
Posted 23 June 2012 - 06:40 PM
Edited by Biglead, 23 June 2012 - 06:41 PM.
#32
Posted 23 June 2012 - 06:41 PM
I live in a fair sized apartment and our modem is set up in another room. instead of wireless, we ran a long assed cord to the computer room. We just tucked it up to the wall by the floor, a few tacks to hold it in place, and we have no problems with connectivity.
#33
Posted 23 June 2012 - 06:50 PM
Biglead, on 23 June 2012 - 06:40 PM, said:
I'm presently on 100ft, and all pings are >1ms, with absolutely no packet loss.
Also, OP, there's another problem with wireless that I'm surprised no one has covered: WLAN Autoconfig
This is a program in Vista and Windows 7 (XP had something very similar, but different name), that will disconnect your wireless connection every 60 seconds for a few moments, to poll wireless networks around you. It cannot be turned off.
The result of this is that every 60 seconds, for about 1-2 seconds, your wireless connection drops, resulting in a momentary lag spike, that happens over, and over, and over, and over, and over, every single minute. That's why if you do a constant ping of a router on wireless long enough (say, type ping 192.168.x.x -n 100), it'll look something like this:
Reply from 192.168.1.1: bytes=32 time 40ms TTL=64
Reply from 192.168.1.1: bytes=32 time 40ms TTL=64
Reply from 192.168.1.1: bytes=32 time 40ms TTL=64
Reply from 192.168.1.1: bytes=32 time 40ms TTL=64
Reply from 192.168.1.1: bytes=32 time 40ms TTL=64
Reply from 192.168.1.1: bytes=32 time 40ms TTL=64
Reply from 192.168.1.1: bytes=32 time 40ms TTL=64
Reply from 192.168.1.1: bytes=32 time 40ms TTL=64
Reply from 192.168.1.1: bytes=32 time 40ms TTL=64
Reply from 192.168.1.1: bytes=32 time 1872ms TTL=64
Reply from 192.168.1.1: bytes=32 time 1428ms TTL=64
Reply from 192.168.1.1: bytes=32 time 40ms TTL=64
Reply from 192.168.1.1: bytes=32 time 40ms TTL=64
Reply from 192.168.1.1: bytes=32 time 40ms TTL=64
Even 60 seconds that happens
There are software workarounds for this (two that I'm aware of), but they don't work 100% of the time, even if one of them (WLAN Optimizer) usually does a decent job, and work or not, these program have to constantly run, and represent an extra hassle to wireless.
Edited by Catamount, 23 June 2012 - 06:51 PM.
#34
Posted 23 June 2012 - 06:51 PM
As for the WLAN Autoconfig issue mentioned above.... maybe I'm lucky. I've never seen that.
Edited by Necrodemus, 23 June 2012 - 06:55 PM.
#35
Posted 23 June 2012 - 07:10 PM
Necrodemus, on 23 June 2012 - 06:51 PM, said:
As for the WLAN Autoconfig issue mentioned above.... maybe I'm lucky. I've never seen that.
Everyone has this problem; as I said, it can't be turned off. It's an integral part of Windows Networking, that's no more optional or less present on all machines than Windows Explorer.
If you haven't noticed it, either you don't play games where 1000-3000ms lag spikes matter, or you've just gotten used to your connection behaving that way. I know I was in the latter situation. Eventually I just got used to my games having a huge lag spike for a moment, every 60 seconds. Some games also doesn't reveal it as well as others. In BF2142, it was obvious because the game would literally "pause"; some games gloss over such lag spikes, so they still occur, and you miss any action that takes place in that 1-3 seconds, it just isn't as obvious.
#36
Posted 23 June 2012 - 07:15 PM
Catamount, on 23 June 2012 - 07:10 PM, said:
If you haven't noticed it, either you don't play games where 1000-3000ms lag spikes matter, or you've just gotten used to your connection behaving that way. I know I was in the latter situation. Eventually I just got used to my games having a huge lag spike for a moment, every 60 seconds. Some games also doesn't reveal it as well as others. In BF2142, it was obvious because the game would literally "pause"; some games gloss over such lag spikes, so they still occur, and you miss any action that takes place in that 1-3 seconds, it just isn't as obvious.
Wow, wasn't aware of that. May have to rethink my wireless setup even though its only 4 feet from the modem.
#37
Posted 23 June 2012 - 07:20 PM
I thought I saw some device that plugs into electrical outlets and basically uses your house's wiring as an Ethernet cable. Any thoughts on those things?
#38
Posted 23 June 2012 - 07:21 PM
Biglead, on 23 June 2012 - 07:15 PM, said:
Wow, wasn't aware of that. May have to rethink my wireless setup even though its only 4 feet from the modem.
Like I said, you should be able to see it. Just have CMD/Powershell do a long, constant ping (just append like -n 1000 to the ping command), and every minute or so, you should see a HUGE spike in the ping. If it's only four feet, I'd just grab a cheap 7ft Ethernet cable

In any case, this is something that's been known for years, but for some reason, MS refuses to fix/change it, even though it screws up gamers royally
http://www.google.co...w=1105&bih=1066
IF Wireless is your only feasible option, get WLAN Optimizer:
http://www.martin-ma.../wlanoptimizer/
It works... usually
Edited by Catamount, 23 June 2012 - 07:24 PM.
#39
Posted 23 June 2012 - 07:29 PM
Oh, that was a fun day.
But 100% worth it.

#40
Posted 23 June 2012 - 07:52 PM
LordDeathStrike, on 22 June 2012 - 09:59 PM, said:
early wireless may have had issues with speed and packets, but these days wireless > wired. in most of the usa the new 4g lte > cable internet speeds and quality, and its wireless too, expect within 5-10 years for your broadband to be delivered wirelessly since the infrastructure is so much easies to build and maintain then wires. (just need towers and recievers in the homes, beautifull aint it.)
I live in Australia and we have 4G Wireless Internet services that use the Mobile phone network. I have experienced two different wireless ISP's and came to the conclusion that wireless internet sucks when compared to ADSL2+, which in turn sucks in comparrison to FTN (Fibre to the Node) cable internet. This is why our government is currently rolling out a National FTN network. The main problem with Wireless internet is that it dramaticaly slows down when it is oversubscribed or in some cases you just get kicked off the network untill the traffic reduces.
So in my opinion I would always recomend cables over wireless unless you don't have access to cables. Also if you install your cables properly you don't get rat nests of cable.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users