[jeber]

That's a good point.

I'm confused by this error:

Quote

An error occurred while releasing interface Loopback Pseudo-Interface 1 : The sy
stem cannot find the file specified.

I wonder if it's related to all those "tunnel" connections you have. I'm wondering what would happen if you deleted all the current connections you have and rebooted while wired to the router.

This error makes sense. It's just an explanation for the 169.254.x.x address you're getting:

Quote

An error occurred while renewing interface Wireless Network Connection 3 : unabl
e to contact your DHCP server. Request has timed out.

It would seem to indicate that either DHCP is not enabled in your router or that your PC won't accept a new IP because of the APIPA one that's already in place. When you release and renew your IP, you are connected by ethernet cable to the router, right? You can't do it wirelessly because you want to release the 169.254.x.x address and immediately have the router's DHCP supply a valid one.

Another possibility is that you have a corrupted TCP/IP stack. I'll have to wait until I get home to pull out my info on fixing that since I'm currently at work and the fix takes a while to cover.

[fritz269]

jeber, on Nov 26 2007, 04:05 PM, said:

Your wireless LAN is still locked into an invalid address. Are you trying the ipconfig wired to the router or wirelessly? If wireless, try it connected to the router. Generally you want to set up your network wired, then once it's all good, go wireless.

To release and renew your IP, you'll need to use the command prompt as an administrator.

I should have added; to run CMD as an administrator, Click on Start, type cmd, but this time, don’t press Enter, instead, press CTRL+SHIFT+Enter. You’ll be prompted to approve the action.

I have run IPconfig as administrator but if you see, I get an error message every time. For some reason it will not release or renew the ip. I connected to it hardwired and ran it and got a different IP address but it still would not let me release or renew as administrator. When I connect back to it wirelessly, it goes back to te 169 ip. Starting to really baffle me. I wonder if it has something to do with the wireless connection sometimes dropping out on other wireless networks and not being able to reconnect until I restart the computer. Is is a problem with vista or the hardware?

rlager, on Nov 26 2007, 06:09 PM, said:

I wonder also if in addition to any other type of security (wep, wpa, etc.) if someone has enabled MAC address filtering/restriction on the router. If this is the case - even if you have the correct wep key or passphrase you won't get an IP address unless the MAC address of your network card has been entered into the router as an allowed address. You will connect, everything will seem fine - but you won't get an IP and therefore you won't be able to get to the internet.

Most people don't usually enable both wireless encryption and mac address filtering - but it's certainly not unheard of. Might be something to check on the router if all else fails.

Have you ever connected to this router before with this laptop successfully? In other words - was it working at one time but then stopped, or has it never worked.

I set up the wireless network and double checked the settings to it today and MAC filtering and restriction is not enabled. I did see a little progress today, when I went to go look at the computers that were connected to the router, I saw my computer where as before, there was no sign of this computer connecting to the router. I have never had a successfull full connection to this network using this laptop and router. I seem to connect to most other networks without a problem and right now I have to use my windows mobile device to access the internet on this laptop when I am at work but as you might suspect, it is really slow...I am ready to throw this out the window. This is the only real problem I have had with vista but if I cannot connect to the network at work then I might have to switch back to xp

[fritz269]

jeber, on Nov 26 2007, 06:46 PM, said:

That's a good point.

I'm confused by this error:

Quote

An error occurred while releasing interface Loopback Pseudo-Interface 1 : The sy
stem cannot find the file specified.

I wonder if it's related to all those "tunnel" connections you have. I'm wondering what would happen if you deleted all the current connections you have and rebooted while wired to the router.

This error makes sense. It's just an explanation for the 169.254.x.x address you're getting:

Quote

An error occurred while renewing interface Wireless Network Connection 3 : unabl
e to contact your DHCP server. Request has timed out.

It would seem to indicate that either DHCP is not enabled in your router or that your PC won't accept a new IP because of the APIPA one that's already in place. When you release and renew your IP, you are connected by ethernet cable to the router, right? You can't do it wirelessly because you want to release the 169.254.x.x address and immediately have the router's DHCP supply a valid one.

I thoght about removing all those "tunnel" connections but I do not know how to do that. I could try to remove all the current connections using the router but does it have to be that router or can it be any router? I thought I did try to renew or release the IP while it was hardwired.

[jeber]

Your problem really has me baffled. I used to work on the help desk for D-Link, and I could almost always get a resolution to a network problem within a few steps, all of which you've already tried. I only have one other suggestion. There's a program that I have installed on all my computers called Network Magic. It doesn't do anything I couldn't do manually, but it does it all from one interface with a single mouse click. Without it I'd have to work in Network Connections, the command line and the router's interface. This program does all that for me. You might download it and give it a try. It's good at telling you what sort of problems it encounters and suggesting fixes. It will even do a network repair for you.

[jeber]

Well, I found an answer to the odd error, "An error occurred while releasing interface Loopback Pseudo-Interface 1" supplied by Bill Castner, a MS-MVP:

Quote

Your command line argument did not specify the interface. As a result, your command requests all interfaces configred to use DHCP to obtain releases, and if configured to use DHCP to isssue new broadcasts.

The error message says that it could not obtain a release by the loopback pseudo interface. The loopback interface by default is 127.0.0.1. It should not be asked a release request in the first place, as it should never have been listed within the DHCP scope of the Vista client.

You can repair this as you would under XP by directly modifying the Route table. One nice thing about the new TCP/IP stack in Vista is that you can use the new DHCP Administrative Tool to edit an expanded scope without fear of misconfiguring your Gateway and Broadcast addresses at the same time.

Whether removing the the duplicate Gateway IPs will resolve this user issues is a seperable issue. It should, however resolve the error message above.

If you're comfortable repairing the route table in either of the two ways he mentions, it should solve the gateway problem. But I'm not comfortable trying to step you through that if you're not sure what you're doing. Perhaps someone with more experience with the Vista DHCP Admin Tool can help.

Another couple of less involved suggestions from other MS folks;

First- go into the network control panel and uncheck ipv6 to see if that helps.
(Control Panel/Network and Sharing Center. Under Network, look for Connection, then Local Area Connection, then View Status (click that). On the Local Area Connection Status page, click on Properties and uncheck Internet Protocol Version 6 in list)

Second- 1. Click on Start button.
2. Type Cmd in the Start Search text box.
3. Press Ctrl-Shift-Enter keyboard shortcut to run the Command
Prompt as Administrator. Allow the elevation request.
4. Type

netsh int ip reset

in the Command window, and then press the Enter key.
5. Restart the computer.

If you aren't comfortable trying these suggestions, I understand. Don't try anything you're unsure of. I'm not sure what to suggest beyond this.

[fritz269]

Gonna try networkmagic first and if that does not work, I will try one of the other suggestions.

[fritz269]

ok, nothing worked. I do not know how to get or use the DHCP administrative tool or how to delete the gateway IP. I tried to imput a manual IP address and that did not work, when I switched back to automatic, the 169 ip came back. Any other suggestions or a walkthrough to the DHCP Admin tool would be much appreciated

[jeber]

Shame on me for not asking the most basic questions first; is this computer connected to the router with a cat5 or cat6 ethernet cable, is it connected to a LAN port on the router, are both connections securely connected, is the router securely connected with the same type of cable to the modem in the WAN port, is this the only computer not able to pull an IP address?

Sorry.

[fritz269]

jeber, on Nov 27 2007, 02:25 PM, said:

Shame on me for not asking the most basic questions first; is this computer connected to the router with a cat5 or cat6 ethernet cable, is it connected to a LAN port on the router, are both connections securely connected, is the router securely connected with the same type of cable to the modem in the WAN port, is this the only computer not able to pull an IP address?

Sorry.

First, this is not connected hardwired. It is a wireless connection I am trying to fix. I have been able to connect hardwired but not wirelessly. I went to borders and had a simular problem except that I was not sending packets but receiving them trying to connect to a tmobile hotspot and could not access the log in page. This is the only computer that I cannot pull an ip address. We have two other laptops connected, one using XP and another using Vista Business and they have no problem. This is what I get when I check the Internet Protocal Configuration. That darn 169 ip wont release and I have tried everything. This is with me using my Windows Mobile Device to connect to the internet but pay attention to the WLAN adapter

Windows IP Configuration


Wireless LAN adapter Wireless Network Connection 3:

Connection-specific DNS Suffix . :
Autoconfiguration IPv4 Address. . : 169.254.48.99
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

Ethernet adapter Local Area Connection 3:

Connection-specific DNS Suffix . : WorkGroup
Link-local IPv6 Address . . . . . : fe80::64f2:6e56:e171:2a49%13
IPv4 Address. . . . . . . . . . . : 192.168.0.102
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1

Tunnel adapter Local Area Connection* 6:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::5efe:169.254.48.99%16
Default Gateway . . . . . . . . . :

Tunnel adapter Local Area Connection* 7:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Local Area Connection* 9:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:4136:e38a:868:3025:3f57:ff99
Link-local IPv6 Address . . . . . : fe80::868:3025:3f57:ff99%11
Default Gateway . . . . . . . . . : ::

Tunnel adapter Local Area Connection* 10:

Connection-specific DNS Suffix . : WorkGroup
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.0.102%22
Default Gateway . . . . . . . . . :

C:\Windows\system32>

This post has been edited by fritz269: 27 November 2007 - 10:49 PM

[jeber]

Try connecting it with an ethernet cable long enough to do the ipconfig /releaseand /renew. See if that will at least restore a valid IP address. As long as you have no connectivity, working wirelessly won't succeed.

[fritz269]

did that and here is the error message once again

Microsoft Windows [Version 6.0.6000]
Copyright © 2006 Microsoft Corporation. All rights reserved.

C:\Windows\system32>ipconfig/release

Windows IP Configuration

An error occurred while releasing interface Loopback Pseudo-Interface 1 : The sy
stem cannot find the file specified.


Wireless LAN adapter Wireless Network Connection 3:

Connection-specific DNS Suffix . :
Autoconfiguration IPv4 Address. . : 169.254.48.99
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Default Gateway . . . . . . . . . :

Tunnel adapter Local Area Connection* 6:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::5efe:169.254.48.99%16
Default Gateway . . . . . . . . . :

Tunnel adapter Local Area Connection* 7:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Local Area Connection* 9:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:4136:e38e:1443:2e1:b4f7:9e2d
Link-local IPv6 Address . . . . . : fe80::1443:2e1:b4f7:9e2d%11
Default Gateway . . . . . . . . . :

Tunnel adapter Local Area Connection* 10:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

C:\Windows\system32>ipconfig/renew

Windows IP Configuration

An error occurred while renewing interface Wireless Network Connection 3 : unabl
e to contact your DHCP server. Request has timed out.
An error occurred while releasing interface Loopback Pseudo-Interface 1 : The sy
stem cannot find the file specified.


Wireless LAN adapter Wireless Network Connection 3:

Connection-specific DNS Suffix . :
Autoconfiguration IPv4 Address. . : 169.254.48.99
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : domain_not_set.invalid
IPv4 Address. . . . . . . . . . . : 75.8.97.210
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 75.8.97.209

Tunnel adapter Local Area Connection* 6:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::5efe:169.254.48.99%16
Default Gateway . . . . . . . . . :

Tunnel adapter Local Area Connection* 7:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Local Area Connection* 9:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:4136:e38c:1c27:2847:b4f7:9e2d
Link-local IPv6 Address . . . . . : fe80::1c27:2847:b4f7:9e2d%11
Default Gateway . . . . . . . . . : ::

Tunnel adapter Local Area Connection* 10:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

C:\Windows\system32>

[fritz269]

I am starting to suspect the wireless card. I have a Realtek 8185. I have another wireless card that I have at home that I am going to try a when I get a chance and see if that works. Anyone think that it might just be a compatability issue with the card or the driver?

[jeber]

It could be. Your wired connection is getting a valid IP now;

Quote

Connection-specific DNS Suffix . : domain_not_set.invalid
IPv4 Address. . . . . . . . . . . : 75.8.97.210
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 75.8.97.209

But the gateway's weird (it should be a private IP like 192.168.0.1) and the IP you're getting isn't from the router, it appears to be from the modem. A LAN IP should be a private address in the ranges 10.0.0.0 - 10.255.255.255, 172.16.0.0 - 172.31.255.255 and 192.168.0.0 - 192.168.255.255.

Try the other card and see what happens. Is it compatible with Vista (does it have Vista drivers)?

[fritz269]

jeber, on Nov 27 2007, 09:02 PM, said:

It could be. Your wired connection is getting a valid IP now;

Quote

Connection-specific DNS Suffix . : domain_not_set.invalid
IPv4 Address. . . . . . . . . . . : 75.8.97.210
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 75.8.97.209

But the gateway's weird (it should be a private IP like 192.168.0.1) and the IP you're getting isn't from the router, it appears to be from the modem. A LAN IP should be a private address in the ranges 10.0.0.0 - 10.255.255.255, 172.16.0.0 - 172.31.255.255 and 192.168.0.0 - 192.168.255.255.

Oh, this was me connected to the modem directly bypassing the wireless router, that might explain

Quote

Try the other card and see what happens. Is it compatible with Vista (does it have Vista drivers)?

I wont be able to get the card until tomorrow and I am not sure if is compatible with vista. Will let you know.

This post has been edited by fritz269: 28 November 2007 - 06:20 AM

[fritz269]

Just wondering if anyone had any other suggestions. Still not working and I tried to go to a TMobile hotspot with the same problem. I could not even get the logging page for that but was able to connect to the router.