- Jan 16, 2001
- 31,529
- 3
- 76
Fck it. I will run 50+ feet of CAT5e, terminate it myself and be done with it.
My DSL router is also a 802.11a/g wireless router. I followed the instructions, created a 128-bit WEP key. Installed a Linksys 802.11g wireless NIC, attempted to configure it.
I got TWO networks but the one I wanted; MINE. I guess they were my neighbors. I found one guys' kid's sofball pics and another guys music. Big deal. I DIDN"T get MY network.
Fcuk it. Tomorrow, I return the wireless NIC and run the damn cable. What a bunch of crap.
I can configure a W2K3 Enterprise network for 1,000+ clients, complete w/DNS/DHCP/SAV/SUS/SMS and database sharing...but I couldn't get my own shiit to work!!! Fck it. WIRED is the way to go.
I already uninstalled the hardware and driver and boxed up the NIC.
This wireless crap seems to have two settings:
1. Wide open. EAsy to configure but you're wide open; i.e. my neighbors
2. Locked down. Safe as food in front of Mary Kate, but impossible for anyone, including me, to get to.:roll:
My DSL router is also a 802.11a/g wireless router. I followed the instructions, created a 128-bit WEP key. Installed a Linksys 802.11g wireless NIC, attempted to configure it.
I got TWO networks but the one I wanted; MINE. I guess they were my neighbors. I found one guys' kid's sofball pics and another guys music. Big deal. I DIDN"T get MY network.
Fcuk it. Tomorrow, I return the wireless NIC and run the damn cable. What a bunch of crap.
I can configure a W2K3 Enterprise network for 1,000+ clients, complete w/DNS/DHCP/SAV/SUS/SMS and database sharing...but I couldn't get my own shiit to work!!! Fck it. WIRED is the way to go.
I already uninstalled the hardware and driver and boxed up the NIC.
This wireless crap seems to have two settings:
1. Wide open. EAsy to configure but you're wide open; i.e. my neighbors
2. Locked down. Safe as food in front of Mary Kate, but impossible for anyone, including me, to get to.:roll: