I got one of these messages the first time as well, but since the address in my case was within my network my network subnet I just said no and ignored it. So far it hasn't happened again. -- Mark

Mark