Re: VPN User - Exchange Resolving to Public IP vs Private
- From: "Ray" <replyhere@xxxxxxxxxxxxxx>
- Date: Mon, 10 Oct 2005 14:30:41 -0400
Hi Lori,
If you're not using a proxy server, the HOSTS file is checked before DNS for
name resolution. It's one of the ways spyware and adware work. If you let
your users have Power User or local administrator rights, the
spyware/adware/viruses will modify the HOSTS file to send the browser to its
sites instead.
If you're using a proxy like Microsoft's ISA server, then the proxy does all
of the name resolution for the client so the HOSTS file won't even be looked
at.
Ray
"Lori" <webmaster@xxxxxxxxxxxxxxx(donotspam)> wrote in message
news:3B823840-CF4D-4C89-9134-D528F6C033FC@xxxxxxxxxxxxxxxx
> Thanks, Ray!
>
> I ended up doing a few hours of research that afternoon - came up w/ 5
> different things to try. 3 needed a reboot but 2 didn't. After I did all
5
> the problem was resolved - without a reboot. So I knew the 1st 3 attempts
> didn't fix it - but I wasn't sure which of last 2 did. One was edit the
> HOSTS file, the other was doing the ipconfig /flushdns. I had assumed it
was
> the /flushdns that fixed it - but I guess it was editing the HOSTS file!
> Well I'm glad to have confirmation on what actually did the trick. Thanks
> again!!
>
> "Ray" wrote:
>
> > LMHOSTS is used for NetBIOS name resolution. If you want to do what you
> > tried to do, you need to modify the HOSTS file instead.
> >
> > Ray
> >
> > "Lori" <webmaster@xxxxxxxxxxxxxxx(donotspam)> wrote in message
> > news:387459EC-C35A-44B7-B57B-50709E8AA6C2@xxxxxxxxxxxxxxxx
> > > Please disregard. A simple "ipconfig /flushdns" cleared up this
problem.
> > >
> > > "Lori" wrote:
> > >
> > > > I have a home user running WinXP Home connecting to our corporate
> > network
> > > > (Win2K) via a VPN.
> > > >
> > > > He's working without a problem with the exception of sporatic
problems
> > > > connecting to our Exchange server (Exchange 2003 on Win2K) via
Outlook.
> > At
> > > > times, he'll be able to launch his email & work without a problem.
> > Randomly,
> > > > Outlook hang and his connection to the Exchange server drops. When
this
> > > > happens, his connection to the other servers remains unaffected.
> > > >
> > > > I found that when this problem occurs, if he pings the Exchange
server
> > he's
> > > > getting the public IP addy. However he CAN ping the internal IP
addy.
> > This
> > > > led me to believe something is wrong with his DNS config. So I set
up an
> > > > LMHOSTS file creating a permanent resolution for our Exchange
server. I
> > > > imported the LMHOSTS file, had him reboot, no dice. When he pings
the
> > > > Exchange server by name he still gets the public IP addy.
> > > >
> > > > I'm completely confused as to what the problem is and how to fix
it....
> > Any
> > > > help would be greatly appreciated!
> >
> >
> >
.
- References:
- Prev by Date: Name can not be resolved.
- Next by Date: Re: Name can not be resolved.
- Previous by thread: Re: VPN User - Exchange Resolving to Public IP vs Private
- Next by thread: Re: VPN User - Exchange Resolving to Public IP vs Private
- Index(es):
Relevant Pages
|
Loading
