Tag Archives: Network

Windows Vista Tip – EnabledLinkedConnections

Windows Vista LogoOn Windows Vista when you map a drive under your admin account you will find that your mapped drive is not available after you switch to your full token via a RunAs or Consent dialog. This is by design because there are actually two tokens in play here. What happens is the LSA recognized that you are admin at logon and creates two logons. The first with a “filtered” token or non-admin which is used to render your desktop and the other containing your full token to be available after consent dialogs.\r\n\r\nBecause there are two separate logons there are separate logon ID’s.  When network shares are mapped they are linked to the current logon session for the current process token. Meaning you don’t have access to the network drive from the alternate logon. This can come into play with logon scripts and a number of other areas where you may require access to a network share from both tokens.\r\n\r\nIf you set the following key it will change how SMB shares are mapped. They will be mapped to a token, which means that LSA will check to see if there is a linked token associated with the user session and add the network share to that location as well. Basically all of this means that after setting this drives will be accessible from both tokens no matter which they are mapped under.\r\n\r\nHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\r\n\r\nEnableLinkedConnections = 1 (DWord)\r\n\r\nDisclaimer: This is not supported by Microsoft and was never tested. Use at your own risk.\r\n\r\nNote: All images, brand names and code used in articles are property of their respective owners. Do not use them without written approval of the respective owner. Windows/ Windows 7 is trade mark of Microsoft Corporation.\r\n\r\n \r\n\r\n \r\n\r\nCredits to: Josh Phillips, Windows Connected

Hello world!

Welcome to Community\r\n\r\nWelcome to SysAdmin community site. You’ll get help, news, discussions and collection of tools for System administration & IT Professionals. The target is to make this community to be one of biggest community of System Administrators and IT Professionals.

Windows 7 Network Disconnects When Idle

Windows 7 Network Disconnects When Idle?\r\n

I am having an issue with the network interfaces (both wired and wireless) disconnecting when the computer is idle for some period of time (~15 minutes from what I’ve observed).

\r\n

This happens both when the computer is plugged into a power source and when running off the battery. It appears the computer is actually turning the interface off (link light on switch port goes off, and WAP shows no association). When the computer is no longer idle (kb/mouse input), the interfaces do automatically come back online without further issue.

\r\n

Having active network traffic (eg. keepalives sent every 60 seconds by an app, like PuTTY) does not prevent the idle timeout from killing the connections. I have verified with a packet sniffer on the remote server that the keepalives are indeed being sent (at least until the interface gets shut down on the laptop).

\r\n

Hardware: Dell Latitude E6400\r\nWired NIC: Intel 82567LM (driver version 10.0.6.0)\r\nWireless NIC: Intel WiFi Link 5300 (driver version 12.4.1.4)\r\nSoftware: Windows 7 Enterprise 64-bit (functionally equivalent to Ultimate version) w/ current OS and driver updates/patches

\r\n

Dell support responded saying Windows 7 is too new and referred me to Microsoft. Microsoft support responded with a couple of power saving config changes (described below) which did not work. Google searches have all yielded one of two answers – the Microsoft suggestion and a registry hack (also described below).

\r\n

Per Microsoft Support:\r\n- Control Panel -> Network & Internet -> Network Connections\r\n- Right-click on desired interface, and select “Properties”\r\n- Click the “Configure” button on the interface properties\r\n- Under the “Advanced” tab, look for power-saving related options and set to “Disabled”\r\n- Under the “Power Management” tab, uncheck “Allow computer to turn off this device to save power”\r\n- Save & Reboot

\r\n

Also per Microsoft:\r\n- Control Panel -> Hardware & Sound -> Power Options\r\n- By the selected power profile, select “Change Plan Settings”\r\n- In the “Edit Plan Settings”, select “Change advanced power settings”\r\n- Under Wireless Adapter Settings -> Power Saving Mode, set options to “Maximum Performance”\r\n- Save & Reboot

\r\n

Per suggestions found on Google:\r\n- Regedit: HKLM\CurrentControlSet\services\LanmanServer\parameters: DWORD: autodisconnect = 0xffffffff\r\n- (same thing as running “net config server /autodisconnect:-1″ from command prompt)\r\n- Save & Reboot

What is IP v6?

Internet Protocol v6, or IPv6, is an Internet layer protocol developed in the 1990s (RFC2460) as an alternative to IPv4. IPv6 is based on 128-bit addresses, meaning that there are 2128 individual addresses available, which is approximately 3.4×1038, and exactly: \r\n

340,282,366,920,938,463,463,374,607,431, 768,211,456\r\nIPv6 provides enough addresses to allow the Internet to continue to expand and the industry to innovate. It is not, however, directly compatible with IPv4, meaning that a device connected via IPv4 cannot communicate directly with a device connected using IPv6.\r\nDeploying IPv6 on a global scale is vital to the Internet industry, but it requires pro-active steps on the part of industry players: technology must be upgraded, staff trained, business plans developed. Uptake to date has been relatively slow, but this is now changing, and businesses need to be aware of the need to adopt IPv6. To ignore IPv6 is to risk your medium to long term business viability.