Tired of ipconfig /release.../renew

[*RedBull*]

I'm tired of doing that some 10 or 12 times in a row only to have it still not connect. I'm on a compaq notebook and sometimes the wireless doesn't get a default gateway so it has limited connection. Is there anyway to get it to connect easier? I don't have this problem in windows vista too much so far. Usually maybe two or three times I might have to repair in Vista but usuallly not. In XP/2K3, I get that problem.

[noroom]

You can use the graphical interface to do the same. Double click on the network connection icon, Support tab, Repair.

Or you can write a batch script, and make a shortcut to it and assign a hotkey to that shortcut.

[dr.bisho]

assign a hotkey ...hmm...ok to that

[+BudMan MVC]

There is NO reason you should have to do anything.. Not getting a default gateway, or not getting a IP all together.. If your seeing an IP address of 169.254 -- that is RANDOM IP that windows gives it self when set for dhcp, but no dhcp server answers.

Creating a hot key to run the ipconfig /renew command or run a repair is NOT the direction you should be looking in.. You should be looking into why your dhcp server does not anwer, etc.

You should connect to your wireless network an get an IP the first freaking time, you should not have to repair or renew anything.

Why don't we fix the root cause of your issue vs finding some lame work around way for you to run /renew easier.

[*RedBull*]

There is NO reason you should have to do anything.. Not getting a default gateway, or not getting a IP all together.. If your seeing an IP address of 169.254 -- that is RANDOM IP that windows gives it self when set for dhcp, but no dhcp server answers.

Creating a hot key to run the ipconfig /renew command or run a repair is NOT the direction you should be looking in.. You should be looking into why your dhcp server does not anwer, etc.

You should connect to your wireless network an get an IP the first freaking time, you should not have to repair or renew anything.

Why don't we fix the root cause of your issue vs finding some lame work around way for you to run /renew easier.

That's what I'm looking for Budman. Using windows repair is the same as manually doing the ipconfig route. I don't want a short cut to it. I want what you described Budman. So tell what I should do to fix the problem.

[Leddy]

What network encryption method are you using? WPA-PSK, or WEP?

[halcyoncmdr]

I am having this same problem as well. I am using WPA2 here. I have been struggling with this for a while as well. One desktop connects just fine wirelessly. But my laptop has problems.

[*RedBull*]

What network encryption method are you using? WPA-PSK, or WEP?

wpa on a Linksys Compact G

[+BudMan MVC]

Well for starters lets get some details.. saying you don't get a default gateway is not much to go on.

I would assume your running dhcp off your router. no some other machine on your network. Lets start with some model numbers, firmware versions and driver versions of your hardware.

Do you loose network connectivity an then it comes back an you do not get an IP.. or is your connectivity fine an your lease just expires?

Please post the details of ipconfig /all -- this will give us lots of info - the make an model of your wireless card, the lease time, etc..

Your 100% sure your not connecting to some other wireless network?

A quick way to verify its a dhcp issue an not a wireless issue is to set a static IP on your wireless client -- if this makes the problem go away an you never have any connectivity issues - then its just dhcp related. If you still have issues connecting, then we are also having wireless issues. Which could be root of the problem.

I would also suggest you take note of your lease time.. note how much time you have left on the lease, when it expires do you loose your connection? ipconfig /all will show you your lease time, etc.

[halcyoncmdr]

I am running a linksys WRT54G v3 with Tomato 1.07. My desktop wireless is running a linksys WMP54G (latest linksys driver) and my laptop is running an internal Broadcom BCM43XX (Something like that, I can't find an exact model number, it is a wireless-n draft, driver 4.102.15.56).

My problem is that when I try to connect to the network I just get assigned a 169.x address. Once I am connected and get a proper 192.168.x address I am fine until I disconnect manually.

Here is my ipconfig /all:

Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Kevin>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Kevin-Laptop
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : hsd1.az.comcast.net

Ethernet adapter Bluetooth Network Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
   Physical Address. . . . . . . . . : 00-16-CF-F5-22-6D
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

   Connection-specific DNS Suffix  . : hsd1.az.comcast.net
   Description . . . . . . . . . . . : Broadcom 802.11n Network Adapter
   Physical Address. . . . . . . . . : 00-19-7E-23-49-A8
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::6416:76d5:af88:249b%9(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.30(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Friday, July 20, 2007 6:16:16 PM
   Lease Expires . . . . . . . . . . : Sunday, July 22, 2007 10:55:21 AM
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 151001470
   DNS Servers . . . . . . . . . . . : 192.168.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : hsd1.az.comcast.net
   Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet
 NIC
   Physical Address. . . . . . . . . : 00-0F-B0-D3-3C-20
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 6:

   Connection-specific DNS Suffix  . : hsd1.az.comcast.net
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::5efe:192.168.0.30%14(Preferred)
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : 192.168.0.1
   NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 10:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
   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. . . . . . . . . : 02-00-54-55-4E-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:0:4136:e37a:10b9:2fd6:3f57:ffe1(Pref
erred)
   Link-local IPv6 Address . . . . . : fe80::10b9:2fd6:3f57:ffe1%13(Preferred)
   Default Gateway . . . . . . . . . : ::
   NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Users\Kevin>

I have it set for a static DHCP on both the desktop and the laptop, but the problem only occurs on the laptop, and turning off DHCP and resetting everything doesn't help either. My lease time is 30 minutes, no relation to my error though.

I am also interested in what all of those tunneling adapters are... :unsure:

[IrfanL]

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : hsd1.az.comcast.net

Description . . . . . . . . . . . : Broadcom 802.11n Network Adapter

Physical Address. . . . . . . . . : 00-19-7E-23-49-A8

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

Link-local IPv6 Address . . . . . : fe80::6416:76d5:af88:249b%9(Preferred)

IPv4 Address. . . . . . . . . . . : 192.168.0.30(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Lease Obtained. . . . . . . . . . : Friday, July 20, 2007 6:16:16 PM

Lease Expires . . . . . . . . . . : Sunday, July 22, 2007 10:55:21 AM

Default Gateway . . . . . . . . . : 192.168.0.1

DHCP Server . . . . . . . . . . . : 192.168.0.1

DHCPv6 IAID . . . . . . . . . . . : 151001470

DNS Servers . . . . . . . . . . . : 192.168.0.1

NetBIOS over Tcpip. . . . . . . . : Enabled

You seem to be connecting to WLAN correctly. But I think you also have Microsoft IPv6 loaded in your protocol stack. If you are not using them, then remove them by going into Local Area Connection's property dialog box, select Microsoft TCP/IP version 6 and click Uninstall. Follow the dialog boxes. When done, repair your connection & see if that helps...

[halcyoncmdr]

I don't have the option to uninstall it. My guess is that is because it is integrated into Windows Vista. :p But I disabled it, so we will see what happens now. Earlier today I didn't have any problems connecting, so hopefully it keeps up. :)

[IrfanL]

Even if the IPv6 is enable I think you should be able to communicate perfectly. There is an advance configuration from which you can assign IPv4 priority over IPv6. But I am not sure where it is located in Windows Vista (if it is).

[halcyoncmdr]

Well, I have no need for it at the moment, so I will just leave it disabled and see if my issues clear up. You never know. I've had things that should have worked perfectly decide not to because they didn't like the day of the week... :p

[*RedBull*]

This is my ipconfig /all....I'm not sure if the IvP6 thing is the ticket. I'm willing to give it a try. I stated that Vista seems to fix the problem but XP/2k3 seem to have problems with no default gateway. It takes numerous times of the old /release /renew to get it locked.

[+BudMan MVC]

If your not using IPv6 then there is no reason to have it running.. an for sure there is NO reason to have it set as your preferred network..

Turn off IPv6 -- see if you still have issues.

http://www.microsoft.com/technet/community...guy/cg0506.mspx

Disabling IPv6

Unlike Windows XP, IPv6 in Windows Vista cannot be uninstalled. To disable IPv6 on a specific connection, you can do the following:

? Add the following registry value (DWORD type) set to 0xFF:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents

This method disables IPv6 on all your LAN interfaces, connections, and tunnel interfaces but does not disable the IPv6 loopback interface. You must restart the computer for this registry value to take effect.

[IrfanL]

Turion, you have an APIPA IP address assigned (169.254.*.*), which means that DHCP service on your network is not working.

[*RedBull*]

So both IvP6 and DCHP are my problem? I'll follow thru witht the IvP6 thing, but the DCHP is I don't know what to do with. It just seem funny that Vista can over come the problem a good bit easier than XP/2k3 can, I mean eventually XP/2k3 will both finally get the connection if I leave it be.

[+BudMan MVC]

IPv6 is sure not helping you in anyway.. look at it like that.

And could be at least part of the problem with getting a dhcp lease.

Disable it -- an see if your issue clears up. If not -- you could try running a different dhcp server. if you have 2k3 you already have a very robust dhcp server.. way more functionality than what your routers dhcp can do - yeah 3rd party firmware does provide for way more features on the dhcp than native.. But they still do not come close to the features of a full blown dhcp server install.

[*RedBull*]

IPv6 is sure not helping you in anyway.. look at it like that.

And could be at least part of the problem with getting a dhcp lease.

Disable it -- an see if your issue clears up. If not -- you could try running a different dhcp server. if you have 2k3 you already have a very robust dhcp server.. way more functionality than what your routers dhcp can do - yeah 3rd party firmware does provide for way more features on the dhcp than native.. But they still do not come close to the features of a full blown dhcp server install.

I easily disabled the IvP (TC/IP) protocal along with other unecessary connections in Vista. It cleared up the problem. I'm going to disable it in XP/2k3 as well. Should hopefully do the trick. Thanks Budman, I'll post again once I've done it.

[*RedBull*]

IPv6 not installed on XP/2k3. What should I do? It seemed to fix the problem in Vista by disabling it.

[+BudMan MVC]

An where did you give the info requested in post #9. Other than 1 screen shot showing one of your machines - which had ipv6 as the preferred interface.

Did you try changing the machine to static? Have you looked at the lease times - does your connection die at renewal? Since your saying 2k3 is having an issue, its clear its not running dhcp.. I have never been really impressed with the dhcp servers included with the routers. Run a REAL one - shoot you have 2k3! It can run a full featured dhcp no problem!

Have you given us the make an model of your devices in question as far as nics, drivers? I did not see this info given.

[*RedBull*]

An where did you give the info requested in post #9. Other than 1 screen shot showing one of your machines - which had ipv6 as the preferred interface.

Did you try changing the machine to static? Have you looked at the lease times - does your connection die at renewal? Since your saying 2k3 is having an issue, its clear its not running dhcp.. I have never been really impressed with the dhcp servers included with the routers. Run a REAL one - shoot you have 2k3! It can run a full featured dhcp no problem!

Have you given us the make an model of your devices in question as far as nics, drivers? I did not see this info given.

I'm running it as workstation. Not sure of how to do what you described. My nic is onboard, I can post that. I was hoping for something easy to fix the problem with though.

[+BudMan MVC]

An if the problem is related to dhcp -- going to static would be a pretty F'ing easy solution now wouldn't it ;)

Yeah its real difficult to install dhcp -- just add the role.. It does not have clue one to what you think your using it as.. An I don't even want to get started on 2k3 as a workstation.. You have a SERVER OS, with all kinds of functionality -- an your using to what play games an watch porn :rolleyes: Let me guess it's the ENT version.. An you forked over $4k for it :rofl:

Turn off the dhcp server on your router - turn it on 2k3 machine.. Point to your router as the gateway in the dhcp settings..

For that matter -- you have a FULL dns server that could actually do some real caching, etc.. an your pointing to your router with what 8mb of ram as a caching name server..

Great to see your putting all the features of that server os to good use :rofl:

[Bgnn32]

Why do you even have a server O/S if your just using as a workstation, that is quite a waste of money.