bluerambo

Distinguished
Nov 2, 2010
97
0
18,640
Hello everyone. I have a gaming machine i ran for some time on a wireless connection. This connection had decent speeds but was unreliable and at times very slow (3000 vent ping). So me and my father fished some cat5e cable through some wall from our router to my room. We used some old external jacks verizon gave us and some 6 foot patch cables to connect the computer and router to the jacks. My problem is that once it was all connected i would plug the cable into my computer but thee computer could not find the connection. After running the troubleshooter it said "LAN connection has invalid IP configuration." Previously I used an ASUS pce-n13 wireless adapter and now the lan is running of the nvidia nforce on my Asus P5n-d motherboard. I am clueless to the problem and I have called Verizon and gotten nowhere. Any input is helpful. Thank you
 
G

Guest

Guest
What type of jacks did Verizon give you? Are they RJ45? Are they wired according to the CAT5 A or B standard? Why are you starting a new thread?
 

bluerambo

Distinguished
Nov 2, 2010
97
0
18,640
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Joe>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Joe-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : myhome.westell.com

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : myhome.westell.com
Description . . . . . . . . . . . : ASUS 802.11n Wireless LAN Card
Physical Address. . . . . . . . . : 70-71-BC-DF-E3-D3
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::d8a5:12e6:8c2e:e9cc%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.46(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, August 28, 2011 12:47:23 PM
Lease Expires . . . . . . . . . . : Monday, August 29, 2011 12:47:23 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 225472956
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-13-3D-D9-20-CF-30-55-8E-BF

DNS Servers . . . . . . . . . . . : 192.168.1.1
192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet
Physical Address. . . . . . . . . : 20-CF-30-55-8E-BF
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::c1c6:1691:782b:4e88%10(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.78.136(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 237031216
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-13-3D-D9-20-CF-30-55-8E-BF

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{EDDBCC13-DE03-4CE6-8645-C8A6053405A3}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:3020:3bf2:b856:e318(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::3020:3bf2:b856:e318%12(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.myhome.westell.com:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : myhome.westell.com
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

C:\Users\Joe>
 

nRRe

Distinguished
Aug 27, 2011
27
0
18,530
Your Wireless is on a private class C address of 192.168.1.0 network with a 255.255.255.0 subnet mask.

But your LAN Ethernet card is set to a class B address of 169.254.78.136. You will have to check your router to verify what IP network it has setup for its LAN connection.

You will possibly have to change that to the 192.168.1.0 network and set default gateway to 192.168.1.1. Try that, set your computer ip to 192.168.1.101 with subnet mask of 255.255.255.0

Again unless your wireless router runs its LAN poets on different network than wireless it should work.
 
G

Guest

Guest
Ignore nRRe. He doesn't know that Windows assigns 169.243.X.X IP addresses when no IP address is assigned by a DHCP server.

Try crimping RJ45 jacks to each end of the ethernet cable using either the A or B wiring standard for each end.
 

nRRe

Distinguished
Aug 27, 2011
27
0
18,530
Ignore nRRe. He doesn't know that Windows assigns 169.243.X.X IP addresses when no IP address is assigned by a DHCP server.

Try crimping RJ45 jacks to each end of the ethernet cable using either the A or B wiring standard for each end.
Harsh way of putting that, but correct.

On my old dlink wireless router I had to manually assign IP addresses for it.

I set it to not broadcast the network and manually assigned IPs as I lved in an apartment complex and I restricted unused addresses. DHCP slipped my mind.

Learned something new today though, thank you.
 
G

Guest

Guest


Sorry to be harsh but incorrect info in posts drive me crazy. Glad you learned something! :D
 
G

Guest

Guest
No, just put RJ45 jacks on the CAT5E cable that you ran from the router to your computer. The order of the wires in the jack must match the CAT5 A or B wiring standard. Then plug one jack into the router and one jack into your computer.
 


It might help if you set the details from the wireless connection into the TCP/IP settings of the ethernet connection as a manual setup to see if that makes the connection work. Just make sure you avoid giving the connection the number 46.

If it does, you could either leave it like that or revert to automatic DHCP because once Windows finds its way, it usually falls into line.




 
G

Guest

Guest


I'm trying to eliminate as many variables as possible. Without knowing anything about the "external verizon wall jacks" I can't say whether they will work or not. Are they RJ45? Are they wired to the CAT5 A or B wiring standard? Sounds like you really don't know what you're doing and should probably get someone familiarar with CAT5 wiring.