Cannot connect using LAN

[castro]

Yesterday, I changed my wireless router from a BT Voyager 2100 to a Speedtouch 716.
I have two PCs and two Laptops using the connection.
All the computers have wireless capability and they all work OK with the Speedtouch router, all connecting to the internet.
My main PC is usually connected via a LAN connection and I cannot get that connection to connect to the internet. It is working ok using the wireless connection albeit at a lowish connection rate. (It is physically a distance away from the router, hence the LAN connection.)
The LAN connection is ok from the PC to the router.
The HomeNetwork diagram on the Speedtouch router is showing the LAN connection as inactive. I cannot get it to become active.
Any ideas please?

When I try to repair the connection I get the message:
Could not renew IP address

[James]

Make sure your local area network connection does not have a static ip set (right click on local area connection in network connections control panel -> choose properties, double click on TCP/IP and choose obtain an ip automatically and obtain dns automatically.

Thats the likely culprit.

Mind you, if you can get to the speedtouch router interface page from your Pc, it's unlikely, but then again, it could just have the wrong subnet mask in the IP settings on your lan card.

Tried a different LAN port on the router? What IP does your PC actually get?

James

[Paul_ADSL24]

Also are you using a straight through or crossover cable?

[castro]

The cable is straight through.
Both IP address and DNS server address are set to auto
I can only connect to the speedtouch router interface page via the wireless connection
I have tried different LAN ports on the router with no difference.
This is the readout from the relevent connection on the router home network page:
RAOPCLAN
Information

Status: Inactive
Type: Desktop Computer
Connected To: ethport4 (Ethernet)

Addressing

Physical Address: 00:13:d4:78:16:6c
IP Address Assignment: DHCP
IP Address: 192.168.1.64
Always use the same address: No
DHCP Lease Time: 0 days, 21:11:58

The computer with the same cable worked ok yesterday with the BT router

[greyrider]

You could also open a command prompt and enter

ipconfig /release

followed by hitting the "enter" key. Note the space twixt ipconfig and the /

[mirage]

Try disabling the wireless connection on the pc that normally connects to the lan Ethernet hardwire port

Right click the wireless icon and choose disable
And then enable local network lan icon
Right click the network icon and choose enable

[castro]

This is the events log from the router. Seems to be lots of Firewalls and LANs

Recorded Events


Time Message



Error 17:09:24 (since last boot) FIREWALL replay check (1 of 1): Protocol: TCP Src ip: 209.85.139.97 Src port: 443 Dst ip: 87.127.97.123 Dst port: 49249


Error 17:09:24 (since last boot) FIREWALL fast tcp state check (1 of 1): Protocol: TCP Src ip: 172.21.223.20 Src port: 11097 Dst ip: 87.127.97.123 Dst port: 49249


Info 17:07:49 (since last boot) UPnP action 'AddPortMapping' from ip=192.168.1.67 (Success)


Info 17:07:49 (since last boot) FIREWALL event (1 of 1): created rules


Info 17:07:49 (since last boot) UPnP action 'DeletePortMapping' from ip=192.168.1.67 (Success)


Info 17:07:49 (since last boot) FIREWALL event (1 of 1): deleted rules


Error 17:02:20 (since last boot) FIREWALL fast tcp state check (1 of 3): Protocol: TCP Src ip: 192.168.1.254 Src port: 80 Dst ip: 192.168.1.66 Dst port: 1248


Error 17:01:13 (since last boot) FIREWALL fast tcp state check (1 of 4): Protocol: TCP Src ip: 72.14.253.91 Src port: 80 Dst ip: 87.127.97.123 Dst port: 53445


Info 17:00:54 (since last boot) UPnP action 'AddPortMapping' from ip=192.168.1.67 (Success)


Info 17:00:54 (since last boot) FIREWALL event (1 of 1): created rules


Info 17:00:54 (since last boot) UPnP action 'DeletePortMapping' from ip=192.168.1.67 (No such entry in array)


Error 17:00:12 (since last boot) FIREWALL fast tcp state check (1 of 2): Protocol: TCP Src ip: 192.168.1.254 Src port: 80 Dst ip: 192.168.1.66 Dst port: 1248


Error 16:59:08 (since last boot) FIREWALL fast tcp state check (1 of 7): Protocol: TCP Src ip: 192.168.1.254 Src port: 80 Dst ip: 192.168.1.66 Dst port: 1248


Info 16:58:55 (since last boot) UPnP action 'DeletePortMapping' from ip=192.168.1.66 (Success)


Info 16:58:55 (since last boot) FIREWALL event (1 of 1): deleted rules


Info 16:58:55 (since last boot) UPnP action 'AddPortMapping' from ip=192.168.1.66 (Success)


Info 16:58:55 (since last boot) FIREWALL event (1 of 5): created rules


Error 16:58:04 (since last boot) FIREWALL fast tcp state check (1 of 29): Protocol: TCP Src ip: 192.168.1.254 Src port: 80 Dst ip: 192.168.1.66 Dst port: 1248


Error 16:56:50 (since last boot) FIREWALL fast tcp state check (1 of 1): Protocol: TCP Src ip: 66.102.9.104 Src port: 80 Dst ip: 87.127.97.123 Dst port: 53414


Info 16:56:33 (since last boot) GRP Default destination is routed via gateway 87.127.97.123


Warning 16:56:33 (since last boot) PPP link up (Internet) [87.127.97.123]


Info 16:56:33 (since last boot) PPP CHAP Chap receive success : authentication ok


Info 16:56:33 (since last boot) PPP CHAP Receive challenge (rhost = j.dsl)


Info 16:56:33 (since last boot) PPP CHAP Receive challenge (rhost = ESR11.Kingston5)


Info 16:56:31 (since last boot) CONFIGURATION saved after running Embedded Setup Wizard (user.tpl deduced from pppdef.tpl.gz)


Info 16:56:29 (since last boot) FIREWALL level changed to Standard.


Warning 16:56:29 (since last boot) DHCS server up


Info 16:56:29 (since last boot) FIREWALL event (1 of 1): created rules


Info 16:56:27 (since last boot) FIREWALL event (1 of 12): enabled rules


Info 16:56:26 (since last boot) GRP Default destination is not routed anymore via gateway 87.127.97.123


Warning 16:56:26 (since last boot) PPP link down (Internet) [87.127.97.123]


Warning 16:56:26 (since last boot) DHCS server went down


Info 16:56:26 (since last boot) FIREWALL event (1 of 1): deleted rules


Info 16:56:26 (since last boot) FIREWALL event (1 of 68): modified rules


Info 16:56:24 (since last boot) FIREWALL event (1 of 1): disabled rules



Pick a task...

[castro]

The "ipconfig /release" had no effect.
I have disabled the wireless connection and tried to both enable and repair the LAN connection.
It just stalls and reports that it cannot renew IP address

[mirage]

with the lan network enabled and the wireless disabled reboot the pc

if that fails to connect to the network try using the network wizard

[castro]

Thanks mirage.
Tried all what you suggested. Still no joy.

[mirage]

very strange i would have expected it to connect,
maybe its a faulty unit
will the same happen if you try connecting a laptop to any of the ethernet ports on the router

[shone1977]

have you tried a hardware reset somewhere on the back you might to use a pen or paper clip!
press in and hold for 30 sec.

[castro]

Yep. The laptop has exactly the same problem.

[Paul_ADSL24]

Copy and paste the output from ipconfig /all please

[castro]

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

Windows IP Configuration

Host Name . . . . . . . . . . . . : RAO
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : lan
lan

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
Physical Address. . . . . . . . . : 00-13-D4-78-16-6C
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.64
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254
Lease Obtained. . . . . . . . . . : 26 March 2007 20:25:44
Lease Expires . . . . . . . . . . : 27 March 2007 20:25:44

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010 PCI
Gigabit Ethernet Controller
Physical Address. . . . . . . . . : 00-13-D4-78-17-7A

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : ASUS 802.11b/g Wireless LAN Card
Physical Address. . . . . . . . . : 00-11-D8-06-C2-37
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.65
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254
Lease Obtained. . . . . . . . . . : 26 March 2007 20:25:37
Lease Expires . . . . . . . . . . : 27 March 2007 20:25:37

[Paul_ADSL24]

Ok. Nothing wrong there then. Disconnect the wireless and then copy and paste the output from tracert www.bbc.co.uk and tracert 212.58.224.86.

Also do you have a software firewall on your PC. If so prevent it from loading at startup and reboot and retry the tests

[castro]

I tried the tracert tests but they did not work without the connection being made via the wireless link. I stopped the firewall loading at startup and rebooted but with the same result.
The strange thing is that last night I did a factory restore and the LAN connection was working. When I switched the PC on this morning it wasn't and I cannot replicate that condition today.
I've checked and the computers still work ok with the BT router. So it's either a faulty router or the settings are not correct.
The LAN connection is ok between the PC and the router and is connected as normal. It just will not connect to the internet.

[Paul_ADSL24]

And did you try all the ports on the router as suggested earlier?

[castro]

Yep.
The bit I can't understand is that the router homepage shows the Lan connection is ok and the computer shows the connection to the router is ok but for some reason when I try to connect to the internet it keeps coming back with the message:
"Could not renew IP address"
Anyway, I am back with the BT Router for the time being.

[Paul_ADSL24]

So what happens if you set a static IP address.

IP Address:- 192.168.1.100
Subnet Mask:- 255.255.255.0
Default Gateway:- 192.168.1.254
DNS Server 1:- 84.234.17.150
DNS Server 2:- 84.234.17.153

Also I did ask for the output from the 2 tracert's as this would have provided me with further information as to the cause of the problem.

[castro]

I set the static IP address and other settings and it now works.
I'm not sure what this means.
Could you possibly explain please.
Will this router never work with auto setting?
Are there any more tests that I can run?

[Paul_ADSL24]

If it's working I would leave it. I have all my PCs on static addresses.

Yes there is further testing but unless you're in the habit of moving your desktop from house to house, swapping your router on a regular basis, or planing on adding 30+ clients to your network then it probably isn't worth it.

[castro]

Are these static addresses unique to you?
Also, having set these static addresses on my PC, the other LAN connection, which I can use with my laptop has also started working, but these addresses are still set to automatic.
The other anomaly that still exists is that I cannot get to the speedtouch welcome page using the LAN connection. If I enable the wireless connection then it finds it OK.

[Paul_ADSL24]

Are you on Vista??

There's an issue with the new IP stack in Vista and the Speedtouch's. Speedtouch should be releasing a fix for this at some point.

It probably doesn't explain why the wireless works but all the people I know of who have had this problem are using LAN connections rather than wireless.

Those static addresses (192.168.1.x) can be used by anyone as they are part of a special non-routable block.

[castro]

Hate to say this but I'm back to square one.
Computer was left in hibernation mode from about 14.00 to 17.00
When I powered up I couldn't connect to the internet as before.
The PC and router are talking to one another ok but the connection is showing as inactive.
The static settings remain as you stated.
All wireless connections remain excellent.
Is there anything else I can do?
My operating system is xp not vista.

[James]

I presume you have rebooted since it hibernated? Hibernation is never good for a PC in my opinion - it always wakes up flaky!

[castro]

I have done a PC reboot and still cannot connect.
Do I give up?

[James]

Maybe a firmware upgrade might help. If you are still having problems - then its either try another network card/PC or router :(

[mirage]

I would be very careful trying a firmware update over a wireless connection
It’s not recommended; one clinch and the router would become a door stopper
Best to (RMA) the unit and try another one….

[James]

Thats true. Never on wireless.

James

[greyrider]

And..castro mentions a PC reboot but not a router one - not a factory reset a la paper clip jobbie, just power off and back on.
Check also that the network card isn't powering down, Control Panel/Network Connections (select your lan connection and hit properties) Configure (next to the lan card) /Power Management

[castro]

The power management box was checked so I unchecked it.
No change .
I switched the PC off.
I unplugged the router.
I switched the router back on.
I switched the PC back on.
The LAN connection now works.
Now as to whether that is a result of the PC reboot or the Router reboot, I know not.
Does unchecking the LAN power management box not take effect until a reboot?
Anyway, at the moment it's ok.

[greyrider]

Uhh...dunno, wait till it hibernates and see what happens, but, in the meantime, HUZZAH!

[castro]

I'm not very sure about this but I will try to explain something.
I have two LAN cables. One goes to the PC and the other goes to either a belkin extender or a laptop.
When I got a LAN connection to the PC after removing power from the router, I connected the second LAN cable to a laptop. I got a message on the PC saying IP address system conflict and the PC lost internet connectivity. I disconnected the second cable, switched the router power off and then on and the connection returned.
Could this second LAN cable be the cause of the problem?

[Ircsum]

I can't recall all the things you've tried but it sounds as though the router is giving the same address to 2 machines. Have you tried turning off DHCP on the router and giving each of the machines a fixed IP?

Ircsum.

[James]

Also make sure you are not setting the same static IP for both machines...

[Paul_ADSL24]

Could this second LAN cable be the cause of the problem?


Yep. You've got the same IP address on the end of the second cable as you're trying to use on your PC. Change one of them and make sure they're all UNIQUE

[castro]

This is becoming a saga!
What I have now found is that I can set the IP address and DNS server address to auto, reboot the router, and the LAN connection works.

Yesterday afternoon, I changed the addresses to auto, rebooted the router and the connection became active.
Yesterday evening, I switched the PC off and switched on again 3 hours later, but the LAN connection then showed connected but inactive.
This morning I switched the PC on and it remained inactive.
I rebooted the router and it became active.
I rebooted the PC twice and it remained active.
I will wait and see what happens next and let you know.

[Ircsum]

As long as you're viewing it as a saga you might like to look into possible hardware compatibility issues, i.e. between router & NIC manufacturers' chipsets/firmware. ;)

Ircsum.