Mikkel Z. Herold skrev:
> Any idea what is going on, and how I can solve this problem?
I found the solution: At the bottom of
http://support.microsoft.com/kb/q303650/ it says
"This workaround does not work for UNC or file:// addresses that use an
IP address. For example, Internet Explorer identifies
\\157.54.100.101\share, or file://157.54.100.101/share, as being in the
Internet zone, even if you add the appropriate IP address range to the
Local Intranet Sites list. In this case, you must use a file:// URL that
has the NetBIOS name (for example, \\server\share) for the site to be
identified in the Local intranet zone."
And I had used the IP address of my server to map the network drives.
The solution was to disconnect from all network drives and reconnect
with the NetBIOS name instead of the IP address.
So, instead of mapping the drive letter to \\192.168.1.100\myshare, I
use \\myservername\myshare, and after adding \\myservername to the list
of intranet sites, my network drives are identified correctly as
belonging to the Intranet zone!
Hope this can help other people
Mikkel
--
"At first just a rustle of canvas
And the gentlest breath on my face"
Sting, "The Wild Wild Sea"