Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Can connect to router and LAN but not internet


  • Please log in to reply

#1
Ben Kent

Ben Kent

    New Member

  • Member
  • Pip
  • 4 posts
Hi,

I am having a strange networking problem. I am using powerline AV (TP-Link TLPA211) to connect an old xp machine in a room that doesn't get my wireless signal. The powerline network seems to work as I have connected other computers and it is working just fine.

The problem I am having is that I can connect to the router (D-Link DIR 655); I can ping it, reach it's config page and also ping all the other devices on my network. I just cannot access the internet.

I don't think it is a dns issue as I cannot access the internet using IP addresses or ping any external IP addresses. I have checked for IP conflicts and tried both DHCP and a static IP. The router accepts the machine into the network just fine, but something is preventing access to the outside world.

I have tried turning off the windows firewall to no avail also.

I tried plugging in a USB wireless card and can connect to the internet via wi-fi through the same router with no problems (it's not an ethernet problem with the router as I have other computers connecting through the ethernet ports just fine.

I have checked all the proxy settings and dns settings on the xp machine and there is nothing unusual there.

I can't think of anything else to try, could it be a bad nic?

Any ideas?

Thanks for your help.

Here is the contents of ipconfig /all:

Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Ben>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : EASTWING
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : hsd1.mn.comcast.net.

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . : hsd1.mn.comcast.net.
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Eth
ernet NIC
Physical Address. . . . . . . . . : 00-11-D8-01-5D-49
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.108
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Monday, December 12, 2011 12:52:46 P
M
Lease Expires . . . . . . . . . . : Monday, December 19, 2011 12:52:46 P
M

C:\Documents and Settings\Ben>
  • 0

Advertisements


#2
Ben Kent

Ben Kent

    New Member

  • Topic Starter
  • Member
  • Pip
  • 4 posts
Upon further inspection I found that when I ping, it resolves an IP address and then times out. I have also fount that whilst I can ping from this computer to the other devices on my network, I cannot ping to this computer. The requests just time out.

I also tried to connect from this computer using Ubuntu on another partition and I cannot connect that way either.

Edited by Ben Kent, 12 December 2011 - 05:14 PM.

  • 0

#3
Ben Kent

Ben Kent

    New Member

  • Topic Starter
  • Member
  • Pip
  • 4 posts
I did a clean install of Windows and am still having the same problem. I therefore conclude that my nic is bad. I have ordered a new nic, and will see what happens.
  • 0

#4
Ben Kent

Ben Kent

    New Member

  • Topic Starter
  • Member
  • Pip
  • 4 posts
Yep, so it turns out it was the NIC. I bought a new one and the connection is working just fine now.

Thanks for your help,

Ben
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP