up vote 17 down vote favorite
7
share [g+] share [fb]

I keep getting this irritating warning when copying files over the network:

These files might be harmful to your computer

These files might be harmful to your computer

Your internet security settings suggest that one or more files may be harmful. Do you want to use it anyway?

I am copying a file from \\192.168.0.197\c$ (home server) to my local machine which is at \\192.168.0.4.

How do I turn off this meaningless "warning"?

link|improve this question
71% accept rate
feedback

4 Answers

up vote 15 down vote accepted

I found a fix by changing "internet options" -- so I guess Windows is detecting the "internet" as my own network.. sigh.

  • Click Start / Control Panel / Internet Options
  • Click Security tab.
  • Click Local Intranet
  • Click Sites button.
  • Click Advanced button.
  • Enter the IP Address of the other machine or server and click Add
  • Click Close

Changing Internet Options screenshot

This worked for me, but it's a bummer I have to manually enter IPs here.. it would be nice if Windows could detect this is a local network file copy and skip the irritating (and pointless) warning about "dangerous" files.

link|improve this answer
I'm curious what you network adapter settings are (ipconfig /all) - It should be catching those addresses under "Automatically detect intranet network". – Darth Android Jun 5 '10 at 8:34
If you use names for the computers (i.e. not IP addresses) then the default rules for local intranet (those three "include..." checkboxes) should apply. – Richard Jun 5 '10 at 9:51
@Richard They should apply anyways, I have a number of windows system which I just reference by IP address and they copy files just fine. – Darth Android Jun 5 '10 at 10:09
Does anyone know if this is a sort of operation that could be scripted for application on multiple computers? Or where the first step to look for that would be? We map all our network drives by IP and it would be great to apply this fix as a script rather than manually. >> edit >> here is a start support.microsoft.com/kb/303650 – bsigrist Jun 16 '11 at 15:36
note @gerbenny answer at the bottom about wildcards in the sites dialog. – IgalSt Aug 1 '11 at 9:04
feedback
up vote 11 down vote

Using Windows 7, I added my IP address with a wildcard:

10.55.25.*

Now all the ip's in this range are part of the "Local Intranet".

link|improve this answer
4  
ah, good tip, it is not clear that dialog supports wildcards. – Jeff Atwood♦ Apr 23 '11 at 10:56
feedback
up vote 2 down vote

I believe you wouldn't get the warning if you used the netbios name of your home server instead of the ip address. If you use the ip address or say the fully qualified dns name of the remote computer it doesn't recognize it as being in the intranet zone. the other option as mentioned earlier is to manually add it to the intranet zone list.

link|improve this answer
feedback
up vote 2 down vote

We recently put in a new server using DFS and I was having this same error. I ended up putting in:

" \\\servername.local.?"

After clicking add, it then showed:

file://*.servername.local.

I tried the * verses the ?, but that was not allowed.

link|improve this answer
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.