Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Outlook unable to connect to exchange server after change in ISP
0 views
Skip to first unread message
V C
Dec 10, 2009, 3:36:02 PM12/10/09
to
Gurus,
We have a windows 2003 server and exchange 2003 server at corp site and
windows 2003 server at a remote site (under same domain). Users in remote
site use MS Outlook and connect to our Exchange server at corp. Everything
worked fine. We just today changed the ISP at remote site, I thought all we
will have to do is change the IP addresses in sonicwall firewall, which I
did. But now users are unable to connect their Outlook. It just keeps on
showing the status as trying to connect..... and nothing happens. I am really
frustrated. Where am i going wrong? Please help. URGENT!!!
thanks in advance.
We have a windows 2003 server and exchange 2003 server at corp site and
windows 2003 server at a remote site (under same domain). Users in remote
site use MS Outlook and connect to our Exchange server at corp. Everything
worked fine. We just today changed the ISP at remote site, I thought all we
will have to do is change the IP addresses in sonicwall firewall, which I
did. But now users are unable to connect their Outlook. It just keeps on
showing the status as trying to connect..... and nothing happens. I am really
frustrated. Where am i going wrong? Please help. URGENT!!!
thanks in advance.
Lanwench [MVP - Exchange]
Dec 10, 2009, 3:52:36 PM12/10/09
to
V C <V...@discussions.microsoft.com> wrote:
> Gurus,
> Gurus,
<affects beatific expression>
So, you have a VPN or MPLS or something connecting these two networks,
right? Is it still functional? Can they ping the Exchange server's LAN IP?
Its NetBIOS name? Did you make all the appropriate changes in the VPN when
the remote site IP address changed?
Is the remote server a DC?
How are the workstations configured - are they members of the domain? Are
they using plain old MAPI to connect, or RPC over HTTP?
V C
Dec 10, 2009, 5:21:01 PM12/10/09
to
Lanwench,
Thanks for replying. No actually we don't have any VPN/MPLS/RPC over HTTPs.
Yes the workstations are connected to the domain as we have a DC at the
remote site too. Outlook was able to connect to the Exchange server till we
made the ISP switch. What exactly am I missing here?
Thanks for replying. No actually we don't have any VPN/MPLS/RPC over HTTPs.
Yes the workstations are connected to the domain as we have a DC at the
remote site too. Outlook was able to connect to the Exchange server till we
made the ISP switch. What exactly am I missing here?
thanks.
> .
>
Lanwench [MVP - Exchange]
Dec 10, 2009, 5:38:51 PM12/10/09
to
V C <V...@discussions.microsoft.com> wrote:
> Lanwench,
> Thanks for replying. No actually we don't have any VPN/MPLS/RPC over
> HTTPs. Yes the workstations are connected to the domain as we have a
> DC at the remote site too. Outlook was able to connect to the
> Exchange server till we made the ISP switch. What exactly am I
> missing here?
> Lanwench,
> Thanks for replying. No actually we don't have any VPN/MPLS/RPC over
> HTTPs. Yes the workstations are connected to the domain as we have a
> DC at the remote site too. Outlook was able to connect to the
> Exchange server till we made the ISP switch. What exactly am I
> missing here?
OK - is it a leased line between the offices, then? How are they connected
at all?
Post an unedited ipconfig /all from a DC in each location (label them
accordingly), and from one of the problem clients.....
0 new messages