Outlook 2003 over VPN on XP client delay

  • Thread starter Thread starter JDTHREE [MVP]
  • Start date Start date
So is the best practice to simply change host names externally to
alleviate any problems resolving names for machines that have both
internal and external functions?

We don't manage our external DNS, but we have our own internal DNS
servers. I never create a forest / domain name that matches the real
public domain.

I'm not sure how I would handle your situation.
 
HI John

Thanks so much. I definately already have the FQDN and that is correct. I also definately have amended the correct host file to show the server IP address and IP name (I suprised myself as I'd been taught how to do this 1.5yrs ago!! - bit of fumbling but it all came back!)

I have to plead dumb when it comes to ipconfig / flushdns however. I know you can type ipconfig into the command prompt and get info on the local computer IP, subnet mask etc. Is there anything I'm meant to edit here, or this command is just to retrieve info? I'm not sure what flushdns is or how to "do it"! Could you elaborate

I think I'm nearly there but not quite!! Going a little out of my mind!

ta
jan
----- JDTHREE [MVP] wrote: ----

On Thu, 11 Mar 2004 23:51:07 -0800, "jhalprin

Hi Jane. FQDN is Fully Qualified Domain Name. So if you have a mai
server named "mail1" and your active directory domain is, say
"domain1.com" then the FQDN of your mail server would be
mail1.domain1.co

I had tried this a few times before, but it didn't work. one thing
did was the ipconfig / flushdns before trying to connect to the mai
server via the VPN after changing my DNS to point to my interna
server. I didn't really do anything new this time that I hadn't don
before, i think it was just the order that I did it this time afte
getting irritated. :) Might also be that I hadn't deleted my lmhost
file the prior times testing. Beat at a computer long enough
eventually it becomes submissive again.

So for the hosts file - depending on operating system, it's located a
either
c:\windows\system32\drivers\etc (XP client, for example
o
c:\winnt\system32\drivers\etc (2000 client for example
o
c:\windows (9x/ME client for example

the hosts file is a plain text file that has the IP of a machine, an
the name of the machine after it. I use tabs between IP's and names
to keep the lineup consistent. For example

216.109.127.60 mail.yahoo.co
131.107.8.43 mail.microsoft.co

You get the idea. As far as "pointing it to the right locations" h
meant to ensure that the entries were correct - that they containe
the correct IP address.

hope this helps

Joh
 
[Please hit the Enter key every 72 characters or so.]
Thanks so much. I definately already have the FQDN and that is correct. I also definately have amended the correct host file to show the server IP address and IP name (I suprised myself as I'd been taught how to do this 1.5yrs ago!! - bit of fumbling but it all came back!).

I have to plead dumb when it comes to ipconfig / flushdns however. I know you can type ipconfig into the command prompt and get info on the local computer IP, subnet mask etc. Is there anything I'm meant to edit here, or this command is just to retrieve info? I'm not sure what flushdns is or how to "do it"! Could you elaborate?

Inspect the output of:
ipconfig /?
 
According to this article you should be lucky you have a connection at all
<http://support.microsoft.com/?id=824123>

That article seems indeed to suggest that OL11 cannot connect to an
Exchange Server trough a VPN at all, which is patently untrue. Just goes
to show how much they know.

Thanks to Leythos and JDTHREE for their work on the DNS front. I'm going
test that and put it into practice next week.
 
there are several
issues with Outlook 2003 and VPN and it appears to be a problem with on
which subnet you are. If you are on the same subnet as the Exchange server
all seems to work well.

If you don't know about the subnets it's best you ask your administrator
about it.

--
Roady [MVP] www.sparnaaij.net
Microsoft Office and Microsoft Office related News
Also Outlook FAQ, How To's, Downloads and more...

Tips of the month:
-Save Embedded Pictures in Their Original Format
-Create an Office XP CD slipstreamed with Service Pack 3
 
there are several
issues with Outlook 2003 and VPN and it appears to be a problem with on
which subnet you are. If you are on the same subnet as the Exchange server
all seems to work well.

If you don't know about the subnets it's best you ask your administrator
about it.

Actually, you don't want your local subnet to be the same as the remote
subnet range. I always avoid using 192.168.0 through 192.168.9 for
business since so many home units default to them.
 
You misunderstood; I'm talking about the IP address of the VPN and the
Exchange server not your internal networkcard

--
Roady [MVP] www.sparnaaij.net
Microsoft Office and Microsoft Office related News
Also Outlook FAQ, How To's, Downloads and more...

Tips of the month:
-Save Embedded Pictures in Their Original Format
-Create an Office XP CD slipstreamed with Service Pack 3

-----
 
Back
Top