.NET 2.0 apps think they're being run from the Internet, but they're being run from the intranet...

[WATYF]

I have several VB.NET apps that run from network shares (and which
have done so for years). In order to make this possible, I increased
the LocalIntranet zone trust level to "FullTrust". This has always
worked just fine.

Recently, and for reasons unknown, all of my apps that run from the
intranet are giving me warnings like so:

"Microsoft .NET Security Warning - Never enter personal information or
passwords into a window unless you can verify and trust the source of
the request"

If I try to open the projects for these applications in VS.NET, I get
a warning saying that I may experience problems running the code,
because the project is on an untrusted location.

After some testing, I figured out that the applications (which have
been running for years off of my intranet shares and have always
worked just fine) now all of a sudden think that they're being run
from the internet. At the top of the form for the applications, the
Form title is prefaced with "Internet - ", and if I set the Internet
security zone to "FullTrust", then all of the problems and warnings go
away.

Obviously, I can't keep my Internet zone at FullTrust, so I need to
figure out what caused this change so I can undo it.

What's even more odd is that this is only happening on my Windows XP
machine. I have a W2K machine as well, which is also setup with the
same zone trust settings, and the code still runs just fine on that
one.

Does anyone have the slightest idea what would cause this?

WATYF

[Jediah L]

Do you happen to use fully qualified domain names to reference the remote
machine (ex: server.domain.local)? If so, does the problem go away if you
use just the netbios name (server).

"WATYF" <WAT...@gmail.com> wrote in message
news:153c837f-1594-40f0...@2g2000hsn.googlegroups.com...

[WATYF]

I found the cause of this... thanks for pointing me in the right
direction.

It ends up that my IT dept (in all their infinite wisdom) changed how
certain shares were auto-mapped so that it was done using the full
domain (instead of the UNC path, which is how they used to do it). If
I manually map the drive using the UNC path, the problem goes away.

WATYF

[Jediah L]

There seems to be some randomness too on how certain machines interpret FQDN
in zones, I think it might have to do with security patches - although I've
never entirely figured it out.

For more information on this (at least documentation on how it is supposed
to configure and work), you can check out:
http://support.microsoft.com/kb/303650

Glad that helped point you to the problem!

Jediah L.

"WATYF" <WAT...@gmail.com> wrote in message

news:dc022631-f5e8-4309...@m3g2000hsc.googlegroups.com...