Sharing is Caring

Here's one because I thought I wouldn't forget and three months later, I forgot. Now I can search for it here.

Many Windows tools use a network share to store information that's needed by various clients. For example, ClearCase uses a network share to hold the storage area for VOBs and views. The path is registered as UNC (e.g., \\mycomputer\myshare) so that all clients can access the data. In fact, if you use a client application that is hosted by the same machine that hosts the share, the client will often still try to access the share via UNC instead of the local path.

I've found that if I have an XP laptop that is a part of a domain, but not always attached to the domain, then even the local shares aren't necessarily visible when disconnected from the network. This will stop ClearCase from performing properly when I'm out demonstrating it.

But there is a workaround. Note that the normal caveats and disclaimers apply. Read the MS knowledge base article to see how you might be messing up your system before you try this:

1. Use Registry Editor (Regedt32.exe) to view the following key in the registry:
HKLM \System \CurrentControlSet \Services \Tcpip \Parameters

Add the following registry value:

  • Value Name: DisableDHCPMediaSense
  • Data Type: REG_DWORD -Boolean
  • Value Data Range: 0, 1 (False, True) Default: 0 (False)
Description: This parameter controls DHCP Media Sense behavior. If you set this value data to 1, DHCP, and even non-DHCP, clients ignore Media Sense events from the interface. By default, Media Sense events trigger the DHCP client to take an action, such as attempting to obtain a lease (when a connect event occurs), or invalidating the interface and routes (when a disconnect event occurs).

2. Restart your computer.

0 thoughtful messages from friendly readers: