anyone having issue with Vista keep disconnect from Wireles?

I have the same issue

Same here. E1705 with a Intel 4965 N adapter running Vista Business. Primary router is a linksys WRT300N. It is not just my wireless connection though. It is happening with the Broadcom LAN connection also. If I try and disable, the computer freezes and requires a hard reboot. After about 3 long boot cycles it will finally connect again. All it says is Identifying on both Adapters. Neither can connect. It works sometimes and fails others. Sometimes it will even not work at all after a reboot. My pc connects when it wants. I have played with all of the network settings and nothing has changed the end state. I even upgraded the driver that they just released for the 3945/4965 internal adapters, and that changed nothing. Happens with my Dell TruMobile 355 Bluetooth adapter also, where I have to reconnect my devices after each reboot or after an extended period of time. I also have the ATI Mobility Radeon 1400 and my display keeps flickering. I have the latest driver, but it is still happening on both the notebook lcd and my extended Acer monitor that's hooked up to the DVI on the Dell. I am also stuck with Outlook 2007. I cannot read any text in any of the emails i receive in Plain or Rich Text. Html works ok, but not the others. All that will come through is the links contained in the email. I have disabled all add ins for outlook as well as disabled Symantec Corporate AV and that changed nothing. Any ideas? Lastly, I know that it is not a problem with my network because my PDA connects fine wirelessly. There is a solid connection, it's either the Dell adapter or Vista Business. I started with Home Premium and still had issues before the upgrade. Then I formatted and started clean with Vista business and started having wireless issues well before I installed any other applications. I sure hope someone can figure this out because I have not had the notebook for more than a week and I am beginning to lose hope. Thanks.

Yes, I had a similar problem with my wif connection disconnecting as well. i didnt have to reboot but I had to disconnect and reconnect. i fixed my problem by downloading a new driver from Intel's website. Everything works fine now. I also noticed Dell updated to this driver a few days ago as well.

I tried the new intel driver last week when it came out but still no change. I waited every day for them to fix that broken driver link because I was hoping that it would fix my problems. Any other ideas? I also upgraded my WRT300N to the latest firmware, but like i said earlier, its not the network failing.

I have the same exact problem. It seems to happen only when the computer becomes idle for about an hour. It refuses to work until I restart. I'm using ethernet connection right now which doesn't seem to have the problem. Very annoying. I haven't checked whether my driver is old yet, so I'll go do that now and cross my fingers.. EDIT: You guys should try this: http://www.intel.com/support/wireles.../cs-006205.htm I'll try it and tell you if it helps or not.

I checked out that link and appreciate the post. It at least explains why I keep getting the da@@ blue screen of death when I'm using bluetooth for an extended period of time with Skype. I had already made the adjustments suggested for the intel adapter as well as upgrading the firmware on my WRT300N to the latest version prior to reading it though. Some other things I have tried while troubleshooting this issue (with still no luck) are I tried setting my WRT300N to only send out a 802.11N signal and got absolutely no connection between the 2 devices (the Intel 4965 and the WRT300N), but I was able to get a connection with a mixed signal, running 40Mhz on the Wide Channel, and Channel 5 on Standard. I switched the Security to WPA2 Personal TKIP/AES because according to linksys you cannot run a solid 802.11n connection on standard WPA Personal Encryption. The really weird thing is that If I am connected to the router via my LAN cable I should be able to log in through its IP with or without a connection but it won't let me so troubleshooting is very limited when i have no connectivity. Something that may work for some of you is to first get the latest intel driver from Dell (released 4/26/07) That driver comes with a utility that wasn't default on my Dell system at least, and its called the Intel Pro Wireless Utility. Open up the utility and set an association between the wireless adapter and the router by entering the Wireless MAC address (not the LAN Mac address) of the router. Hopefully that will help somebody, but i am still stuck. If anyone figures it out, let me know.

I used to have the same issue. After searching the web, I found someboy fixed same issue by re-seating the card. So I tried it and my M1210 hasn't lost wireless since. The mini PCI slot on DELL laptop is not very tight.

Have any of you guys looked at your event log to see if this conflict comes up. I'm not saying that it is the source of our problems, but it is possible. Technically doing a repair connection should do the trick, but like I have said in previous posts, I cannot ever get it to repair without freezing up. I am wondering if there is a problem with Vista. I got my second notebook from dell and it has the same problem.

Now if it were a DHCP error, that would explain why after restarting a few times the connection will start working again because eventually the DHCP server will give up and issue a new IP. I do not understand though why it doesn't show an IP conflict like on XP. A DHCP error would also explain why the connection goes out after a certain period of time of an active connection. Can anyone verify what their router DHCP lease time is set at and then compare that lease time to when their connection drops? I have mine set at 0 which is a 24 hour lease on the IP. Maybe we could just assign our PC a static IP off of one of the DHCP issuing addresses and choose an IP that is towards the end of the IP range like 192.168.1.150 or whatever your IP range is. Something else we could try would be to run an ipconfig /all like the knowledge base article says and then release/renew the ip. This would only be a temporary fix though becasue the next time the lease expires we will be in the same boat all over again. It makes a lot of sense though. Any ideas or feedback? Anybody with the same event id with the same problem? Anybody's problem fixed temporarily with a DHCP release/renew? Let me know.

Address Conflicts: Event ID 1002
http://technet2.microsoft.com/window....mspx?mfr=true

This documentation is preliminary and subject to change.

DHCP operates on a lease renewal basis. During the leasing process, address conflicts can occur as leases are renewed and expired. Client lease requests might be denied by the server for invalid (out of pool) or duplicate addresses. Multiple address conflict messages can indicate that your lease period, your scope, or both, need adjustment in your DHCP server configuration.

Event Details

Product:
Windows Operating System
ID:
1002
Source:
Microsoft-Windows-DHCP-Client
Version:
6.0
Symbolic Name:
EVENT_NACK_LEASE
Message:
The IP address lease %1 for the network adapter with MAC address %2 has been denied by the DHCP server %3 (The DHCP server sent a DHCPNACK message).

Resolve

Renew the client DHCP lease

The IP address for this computer is the same IP address used by another computer on the network. No user action is required. The DHCP client will attempt to get a new IP address from the DHCP server, or, if the client computer automatically configures its own IP address, it will assign itself a different address.
If you do not want to wait for the client to make its automatic renewal attempt, you can manually release and renew the IP address of the client by following these steps:
1.
At the DHCP-enabled client computer, click Start, click Run, and then type cmd.
2.
Use the Ipconfig command-line utility to verify, release, or renew the lease of the client with a DHCP server, as follows:
To verify a DHCP client lease, type ipconfig /all to view lease-status information.
To release a DHCP client lease, type ipconfig /release.
To renew a DHCP client lease, type ipconfig /renew.
If the problem persists, you might have manually defined static IP addresses to network devices and computers during a network link failure to a DHCP server, and then the link was reestablished.
To resolve this conflict
•Convert the network device with the static IP address to a DHCP client, or, on the DHCP server, exclude the static IP address from the DHCP scope.
To exclude the static IP address from the DHCP scope
1.
Turn off the DHCP client computer that is in conflict with the network device that has the static IP address.
2.
On the DHCP server, exclude the static IP address from the scope of the DHCP IP address range.
3.
Restart the DHCP client computer.
To prevent this problem in the future, consider configuring conflict detection (it is off by default) on your DHCP server. With conflict detection enabled, the DHCP server attempts to ping each available address it intends to offer before presenting the address in a lease offer to a client. This ensures that each IP address offered to clients is not already in use by another non-DHCP computer that uses manual TCP/IP configuration.

Top of page

Verify

To verify that address conflicts have been resolved, perform the following steps:
1.
At the DHCP-enabled client computer, click Start, click Run, and then type cmd.
2.
To verify a DHCP client lease, type ipconfig /all to view lease-status information.
The IP address should be assigned to your computer and should be marked as preferred.
The output of the ipconfig command should show an Internet Protocol version 6 (IPv6) address with formatting similar to the following example:
•IP Address ...... : fec0::f1b1:203:ffff:feb1:f4e3%1 [Public]
•3ffe:2800:d005:f1b1:f517:cdee:53b7:6b04 [Temporary]
•3ffe:2900:d004:f1b1:203:ffff:feb3:f4e3 [Public]
•fe80::203:ffff:feb3:f4e3%6

http://technet2.microsoft.com/window....mspx?mfr=true