Tech Support Forum banner

NIC connection to Netgear router

1255 Views 14 Replies 2 Participants Last post by  johnwill
Hello everybody,
I have an odd problem in connecting my PC to a Netgear DG834PN modem/router,
The system works fine in every way except when I try to address the router.
When I try this the PC tries to connect and sort of succeeds but cannot latch onto the router, it constantly connects and disconnects to a clicking sound.
Device manager says it's working OK and it's driver is the right one.
The system is running Win7, the nic is an Intel 82566DC.

My netbook connects just fine using the same cable.
I'm thinking of buying and putting in another nic.

I'd be grateful for any ideas.

Dimitri456
Status
Not open for further replies.
1 - 15 of 15 Posts
With the cable connected, let's see this.


Hold the Windows key and press R, then type CMD then press Enter to open a command prompt:

In the command prompt window that opens, type type the following command:

Note that there is a space before the /ALL, but there is NOT a space after the / in the following command.

IPCONFIG /ALL

Right click in the command window and choose Select All, then hit Enter to copy the contents to the clipboard.
Paste the results in a message here.

If you are on a machine with no network connection, use a floppy, USB disk, or a CD-RW disk to transfer a text file with the information to allow pasting it here.
See less See more
Hi johnwill,
I've done as you said but after hitting enter at the end nothing seemed to happen.
I couldn't find clipboard, so installed Karen's clipboard viewer and all that appears to be in the clipboard is C:\Users\Art>IPCONFIG /ALL
Thanks so much for your interest.
dimitri456
Sorry johnwill,
Here's the contents of the clipboard
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Art>IPCONFIG /ALL

Windows IP Configuration

Host Name . . . . . . . . . . . . : Art-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82566DC-2 Gigabit Network Connec
tion
Physical Address. . . . . . . . . : 00-19-DB-BB-8A-54
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5195:2725:d8a7:82d7%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 15 July 2010 09:09:35
Lease Expires . . . . . . . . . . : 18 July 2010 09:09:35
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 234887643
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-3C-26-70-00-19-DB-BB-8A-54

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

Tunnel adapter isatap.{7F9FC29B-3EA3-4154-A365-75EBDD08CF9B}:

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 Local Area Connection* 11:

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:5ef5:73b8:2444:12bd:acbc:f430(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::2444:12bd:acbc:f430%13(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Users\Art>
See less See more
Well, that looks like it's connected properly.

Let's add some pings to that test.


Try these simple tests.

Hold the Windows key and press R, then type CMD (COMMAND for W98/WME) to open a command prompt:

In the command prompt window that opens, type type the following commands one at a time, followed by the Enter key:

NOTE: For the items below in red surrounded with < >, see comments below for the actual information content, they are value substitutions from the previous IPCONFIG command output! Do NOT type <computer_IP_address> into the command, that won't work. Also, the < and > in the text is to identify the parameters, they are also NOT used in the actual commands.

Do NOT include the <> either, they're just to identify the values for substitution.

IPCONFIG /ALL

PING <computer_IP_address>

PING <default_gateway_address>

PING <dns_servers>

PING 74.125.45.100

PING yahoo.com

Right click in the command window and choose Select All, then hit Enter to copy the contents to the clipboard.
Paste the results in a message here.

<computer_IP_address> - The IP Address of your computer, obtained from the IPCONFIG command above. (For Vista/Win7, the IPv4 Address)

<default_gateway_address> - The IP address of the Default Gateway, obtained from the IPCONFIG command above.

<dns_servers> - The IP address of the first (or only) address for DNS Servers, obtained from the IPCONFIG command above.

If you are on a machine with no network connection, use a floppy, USB disk, or a CD-RW disk to transfer a text file with the information to allow pasting it here.
See less See more
Hi Johnwill,
Copy below as requested, perhaps to clarify the problem this PC is accessing the net perfectly through the network cable, I'm using it now.
Everything on this PC is working normally except that I can't access the netgear through 192.168.0.1, I wanted to get in to change the security settings.
dimitri456


Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.


C:\Users\Art>ping 192.168.0.2

Pinging 192.168.0.2 with 32 bytes of data:
Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
Reply from 192.168.0.2: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\Art>ping 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64

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

C:\Users\Art>ping 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64

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

C:\Users\Art>
See less See more
Here are the last two,
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Art>ping 74.125.45.100

Pinging 74.125.45.100 with 32 bytes of data:
Reply from 74.125.45.100: bytes=32 time=144ms TTL=53
Reply from 74.125.45.100: bytes=32 time=143ms TTL=53
Reply from 74.125.45.100: bytes=32 time=143ms TTL=53
Reply from 74.125.45.100: bytes=32 time=142ms TTL=53

Ping statistics for 74.125.45.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 142ms, Maximum = 144ms, Average = 143ms

C:\Users\Art>ping yahoo.com

Pinging yahoo.com [98.137.149.56] with 32 bytes of data:
Reply from 98.137.149.56: bytes=32 time=202ms TTL=56
Reply from 98.137.149.56: bytes=32 time=203ms TTL=56
Reply from 98.137.149.56: bytes=32 time=202ms TTL=56
Reply from 98.137.149.56: bytes=32 time=202ms TTL=56

Ping statistics for 98.137.149.56:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 202ms, Maximum = 203ms, Average = 202ms

C:\Users\Art>
See less See more
That looks perfectly normal, are you saying that connection doesn't work?
As I said in my first posting everything seems normal except connecting to the router from a browser
If I try http://192.168.0.1 from explorer the progress bar at the bottom of the screen crawls along taking minutes to get to about 40% where it stops.
If I try to get to it from my favourites where the user name and the password box's are completed this is when it tries to connect and does so but is unable to hold the connection, constantly loading and the loading again but never locking on.
Connection to the router is instant using my netbook and 192.168.0.1.
Whilst playing with this at one point it did lock onto the router from a refresh, but when I closed it and tried again I was back to square one.
I'd be looking for some firewall restriction for connections to 192.168.0.1 on that machine. One thing to try is boot in Safe Mode with Networking and see if you can connect that way.
I gave it a go in safe mode with networking, exactly the same symptoms, I think I'll leave it alone and access the router through another computer if I need to.
If it gets any worse I'll at least have our tries to refer back to.
I'm very grateful for your help and have learnt a lot during our conversations.
Thanks so much
dimitri456
Bummer we can't get that working, that's a really odd issue.
1 - 15 of 15 Posts
Status
Not open for further replies.
Top