Unfortunately WINS was having no luck, that's why I resorted to
LMHOSTS. Outlook is pointing at the FQDN and has no problem within the
physical network, via dial-up and vpn, via via a 3G mobile datacard and
VPN, via isdn and vpn... the list is endless.
I also know that the router (netgear dg834g) works fine with other
laptops.
It's a problem that happens often but never quite in this fashion with
the names apparantly being resolved by everything but exchange (and
SQL)
Ugh.
Brian O'Neil wrote:
First thing I would do is implement WINS to avoid having LMHOST files
out
there. If you're using the Windows RAS Server it should pull this
information
from your DHCP scope if you have populated it there. That will
eliminate 99%
of your remote name resolution problems.
In outlook, have you tried entering in the FQDN of the Exchange
server? That
will force outlook to try DNS name resolution.
-Brian
"rudy carroll" wrote:
Hey, hey.
For the past year I've been having all sorts of problems getting
outlook to connect to exchange via a pptp vpn. This isn't on just
one
set-up either. On many, many diferent configurations of sbs 2000,
sbs
2003. The problem normally goes like this...
Remote machine connects to vpn, can see network shares by ip
address
but not by name - as a resuly can't see exchange server. Ok, you
say.
Easily fixed by editing LMHOSTS. Not always so. Sometimes that has
no
effect although normally solves the problem after a while.
The problem I have now is that the remote machine can see the
network
easily. All names are efficiently resolved to ips by the DNS on the
server, however Outlook can't see exchange still. Also SQL server
traffic won't flow. Outlook express can see the exchange imap
server
by ip but not by name - but everything else is happy with names.
I would so like to get this sorted out once and for all.
All suggestions gratefully received
Ta.
Reply With Quote