OL2007B2 - Cannot Connect To Exchange Through VPN

[Guest]

Ok, here is the setup:

Laptop w/ Windows XP SP2 + All patches. Running clean Office 2007 B2.

Not connected to the LAN, through a cable modem with Netscreen client
version 8.7:

Fired up Outlook 2007, setup profile, do a manual configure, select
"exchange", then type in server name and mailbox name, clikc on "Check"...
gets an error:

An unknown error occurred, error code: 0x90040605

If I connect to the LAN, works. If I connecct wirelessly, works.

Ok, so once connected to the LAN and get it to recognize the mailbox and get
Outlook configured properly, I am now remote. Connect VPN through Netscreen
client. Fireup Outlook... It can never connect to the exchange server.

Frustrated, I uninstall Office 2007 Beta, go back to Office 2003 Pro, set it
all up and all works through the VPN flawlessly. Including setting up
Outlook profiles and such.

So, it seems Outlook 2007B2 is having a problem with VPN connections. We
tested this with the Cisco VPN client and is having the same problem there,
too. When you look at traffic on the PC, it doesn't even try to send it out
the VPN tunnel.

Any ideas? Very strange, as Outlook 2003 didn't care what connection you
had it on, as long as it had a connection.

Jonathan Merrill
MCP, CCA, NET+
www.gomerrill.com

 

[Roady [MVP]]

How are the serverside security settings? It could be configured to only
allow networktraffic from specified applications.
Another one; what version of Exchange is running? Outlook 2007 cannot
connect to Exchange 5.5 and previous.

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003


-----
message Ok, here is the setup:

Laptop w/ Windows XP SP2 + All patches. Running clean Office 2007 B2.

Not connected to the LAN, through a cable modem with Netscreen client
version 8.7:

Fired up Outlook 2007, setup profile, do a manual configure, select
"exchange", then type in server name and mailbox name, clikc on "Check"...
gets an error:

An unknown error occurred, error code: 0x90040605

If I connect to the LAN, works. If I connecct wirelessly, works.

Ok, so once connected to the LAN and get it to recognize the mailbox and get
Outlook configured properly, I am now remote. Connect VPN through Netscreen
client. Fireup Outlook... It can never connect to the exchange server.

Frustrated, I uninstall Office 2007 Beta, go back to Office 2003 Pro, set it
all up and all works through the VPN flawlessly. Including setting up
Outlook profiles and such.

So, it seems Outlook 2007B2 is having a problem with VPN connections. We
tested this with the Cisco VPN client and is having the same problem there,
too. When you look at traffic on the PC, it doesn't even try to send it out
the VPN tunnel.

Any ideas? Very strange, as Outlook 2003 didn't care what connection you
had it on, as long as it had a connection.

Jonathan Merrill
MCP, CCA, NET+
www.gomerrill.com

 

[Guest]

How our network is setup is once you VPN, you can access all ports to any of
our servers. Further, the mail server is not locked down or has any security
templates applied to it. This is a test environment.

And we use Exchange 2003, all patches, all service packs.

Appreciate the response. Outlook 2003 works no sweat under this
configuration, so I am leaning on OL2007B2 having a problem with VPN tunnels.
Anyone else test OL2007B2 through their VPN client?

J. Merrill
MCP, CCA, NET+
www.gomerrill.com

 

[Roady [MVP]]

Can't test this myself as I currently do not have the setup for it but I've
passed it through.

As an additional question; is the VPN client located on the same subnet as
the Exchange server?

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003


-----
message How our network is setup is once you VPN, you can access all ports to any of
our servers. Further, the mail server is not locked down or has any
security
templates applied to it. This is a test environment.

And we use Exchange 2003, all patches, all service packs.

Appreciate the response. Outlook 2003 works no sweat under this
configuration, so I am leaning on OL2007B2 having a problem with VPN
tunnels.
Anyone else test OL2007B2 through their VPN client?

J. Merrill
MCP, CCA, NET+
www.gomerrill.com

 

[Guest]

No, the VPN connection is on another non-routable subnet. This allows us to
log any traffic on that particular subnet coming into our test network.

So, the VPN user subnet would be on a 172.16.x.x.
The test server network is 192.168.x.x.

Also, tested this scenario with the Watchguard VPN client, and it also does
not work.

Appreciate it!

Jonathan Merrill
MCP, CCA, NET+
www.gomerrill.com

Can't test this myself as I currently do not have the setup for it but I've
passed it through.

As an additional question; is the VPN client located on the same subnet as
the Exchange server?

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003


-----
message How our network is setup is once you VPN, you can access all ports to any of
our servers. Further, the mail server is not locked down or has any
security
templates applied to it. This is a test environment.

And we use Exchange 2003, all patches, all service packs.

Appreciate the response. Outlook 2003 works no sweat under this
configuration, so I am leaning on OL2007B2 having a problem with VPN
tunnels.
Anyone else test OL2007B2 through their VPN client?

J. Merrill
MCP, CCA, NET+
www.gomerrill.com

How are the serverside security settings? It could be configured to only
allow networktraffic from specified applications.
Another one; what version of Exchange is running? Outlook 2007 cannot
connect to Exchange 5.5 and previous.

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003
http://www.howto-outlook.com/
Outlook FAQ, HowTo, Downloads, Add-Ins and more

-----
message Ok, here is the setup:

Laptop w/ Windows XP SP2 + All patches. Running clean Office 2007 B2.

Not connected to the LAN, through a cable modem with Netscreen client
version 8.7:

Fired up Outlook 2007, setup profile, do a manual configure, select
"exchange", then type in server name and mailbox name, clikc on "Check"...
gets an error:

An unknown error occurred, error code: 0x90040605

If I connect to the LAN, works. If I connecct wirelessly, works.

Ok, so once connected to the LAN and get it to recognize the mailbox and
get
Outlook configured properly, I am now remote. Connect VPN through
Netscreen
client. Fireup Outlook... It can never connect to the exchange server.

Frustrated, I uninstall Office 2007 Beta, go back to Office 2003 Pro, set
it
all up and all works through the VPN flawlessly. Including setting up
Outlook profiles and such.

So, it seems Outlook 2007B2 is having a problem with VPN connections. We
tested this with the Cisco VPN client and is having the same problem
there,
too. When you look at traffic on the PC, it doesn't even try to send it
out
the VPN tunnel.

Any ideas? Very strange, as Outlook 2003 didn't care what connection you
had it on, as long as it had a connection.

Jonathan Merrill
MCP, CCA, NET+
www.gomerrill.com

 

[Roady [MVP]]

Is it possible for you to test it with the same subnet?
Do you see Kerberos packets being dropped somewhere?
What happens when you switch authentication to use NTLM instead?

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003


-----
message No, the VPN connection is on another non-routable subnet. This allows us to
log any traffic on that particular subnet coming into our test network.

So, the VPN user subnet would be on a 172.16.x.x.
The test server network is 192.168.x.x.

Also, tested this scenario with the Watchguard VPN client, and it also does
not work.

Appreciate it!

Jonathan Merrill
MCP, CCA, NET+
www.gomerrill.com

Can't test this myself as I currently do not have the setup for it but
I've
passed it through.

As an additional question; is the VPN client located on the same subnet as
the Exchange server?

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003


-----
message How our network is setup is once you VPN, you can access all ports to any
of
our servers. Further, the mail server is not locked down or has any
security
templates applied to it. This is a test environment.

And we use Exchange 2003, all patches, all service packs.

Appreciate the response. Outlook 2003 works no sweat under this
configuration, so I am leaning on OL2007B2 having a problem with VPN
tunnels.
Anyone else test OL2007B2 through their VPN client?

J. Merrill
MCP, CCA, NET+
www.gomerrill.com

How are the serverside security settings? It could be configured to only
allow networktraffic from specified applications.
Another one; what version of Exchange is running? Outlook 2007 cannot
connect to Exchange 5.5 and previous.

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003
http://www.howto-outlook.com/
Outlook FAQ, HowTo, Downloads, Add-Ins and more

-----
message Ok, here is the setup:

Laptop w/ Windows XP SP2 + All patches. Running clean Office 2007 B2.

Not connected to the LAN, through a cable modem with Netscreen client
version 8.7:

Fired up Outlook 2007, setup profile, do a manual configure, select
"exchange", then type in server name and mailbox name, clikc on
"Check"...
gets an error:

An unknown error occurred, error code: 0x90040605

If I connect to the LAN, works. If I connecct wirelessly, works.

Ok, so once connected to the LAN and get it to recognize the mailbox and
get
Outlook configured properly, I am now remote. Connect VPN through
Netscreen
client. Fireup Outlook... It can never connect to the exchange server.

Frustrated, I uninstall Office 2007 Beta, go back to Office 2003 Pro,
set
it
all up and all works through the VPN flawlessly. Including setting up
Outlook profiles and such.

So, it seems Outlook 2007B2 is having a problem with VPN connections.
We
tested this with the Cisco VPN client and is having the same problem
there,
too. When you look at traffic on the PC, it doesn't even try to send it
out
the VPN tunnel.

Any ideas? Very strange, as Outlook 2003 didn't care what connection
you
had it on, as long as it had a connection.

Jonathan Merrill
MCP, CCA, NET+
www.gomerrill.com

 

[Guest]

No, not possible. But the curious portion is why Outlook 2003 works
unhindered. This issue only presents itself with OL2007B2.

Also, we are running a sniffer and do not see any packets coming from the
laptop to the exchange server, beyond the usual traffic.

Jonathan Merrill
MCP, CCA, NET+
www.gomerrill.com

Is it possible for you to test it with the same subnet?
Do you see Kerberos packets being dropped somewhere?
What happens when you switch authentication to use NTLM instead?

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003


-----
message No, the VPN connection is on another non-routable subnet. This allows us to
log any traffic on that particular subnet coming into our test network.

So, the VPN user subnet would be on a 172.16.x.x.
The test server network is 192.168.x.x.

Also, tested this scenario with the Watchguard VPN client, and it also does
not work.

Appreciate it!

Jonathan Merrill
MCP, CCA, NET+
www.gomerrill.com

Can't test this myself as I currently do not have the setup for it but
I've
passed it through.

As an additional question; is the VPN client located on the same subnet as
the Exchange server?

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003
http://www.howto-outlook.com/
Outlook FAQ, HowTo, Downloads, Add-Ins and more

-----
message How our network is setup is once you VPN, you can access all ports to any
of
our servers. Further, the mail server is not locked down or has any
security
templates applied to it. This is a test environment.

And we use Exchange 2003, all patches, all service packs.

Appreciate the response. Outlook 2003 works no sweat under this
configuration, so I am leaning on OL2007B2 having a problem with VPN
tunnels.
Anyone else test OL2007B2 through their VPN client?

J. Merrill
MCP, CCA, NET+
www.gomerrill.com

How are the serverside security settings? It could be configured to only
allow networktraffic from specified applications.
Another one; what version of Exchange is running? Outlook 2007 cannot
connect to Exchange 5.5 and previous.

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003
http://www.howto-outlook.com/
Outlook FAQ, HowTo, Downloads, Add-Ins and more

-----
message Ok, here is the setup:

Laptop w/ Windows XP SP2 + All patches. Running clean Office 2007 B2.

Not connected to the LAN, through a cable modem with Netscreen client
version 8.7:

Fired up Outlook 2007, setup profile, do a manual configure, select
"exchange", then type in server name and mailbox name, clikc on
"Check"...
gets an error:

An unknown error occurred, error code: 0x90040605

If I connect to the LAN, works. If I connecct wirelessly, works.

Ok, so once connected to the LAN and get it to recognize the mailbox and
get
Outlook configured properly, I am now remote. Connect VPN through
Netscreen
client. Fireup Outlook... It can never connect to the exchange server.

Frustrated, I uninstall Office 2007 Beta, go back to Office 2003 Pro,
set
it
all up and all works through the VPN flawlessly. Including setting up
Outlook profiles and such.

So, it seems Outlook 2007B2 is having a problem with VPN connections.
We
tested this with the Cisco VPN client and is having the same problem
there,
too. When you look at traffic on the PC, it doesn't even try to send it
out
the VPN tunnel.

Any ideas? Very strange, as Outlook 2003 didn't care what connection
you
had it on, as long as it had a connection.

Jonathan Merrill
MCP, CCA, NET+
www.gomerrill.com

 

[Roady [MVP]]

Can you see at what point they are being dropped? Client level or later? No
clientside firewall that could block the traffic?
VPN to an Exchange server on the same network as an Outlook 2007B2 client
has been verified to work. Still waiting for results for when they are not
on the same network.

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003


-----
message No, not possible. But the curious portion is why Outlook 2003 works
unhindered. This issue only presents itself with OL2007B2.

Also, we are running a sniffer and do not see any packets coming from the
laptop to the exchange server, beyond the usual traffic.

Jonathan Merrill
MCP, CCA, NET+
www.gomerrill.com

Is it possible for you to test it with the same subnet?
Do you see Kerberos packets being dropped somewhere?
What happens when you switch authentication to use NTLM instead?

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003


-----
message No, the VPN connection is on another non-routable subnet. This allows us
to
log any traffic on that particular subnet coming into our test network.

So, the VPN user subnet would be on a 172.16.x.x.
The test server network is 192.168.x.x.

Also, tested this scenario with the Watchguard VPN client, and it also
does
not work.

Appreciate it!

Jonathan Merrill
MCP, CCA, NET+
www.gomerrill.com

Can't test this myself as I currently do not have the setup for it but
I've
passed it through.

As an additional question; is the VPN client located on the same subnet
as
the Exchange server?

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003
http://www.howto-outlook.com/
Outlook FAQ, HowTo, Downloads, Add-Ins and more

-----
message How our network is setup is once you VPN, you can access all ports to
any
of
our servers. Further, the mail server is not locked down or has any
security
templates applied to it. This is a test environment.

And we use Exchange 2003, all patches, all service packs.

Appreciate the response. Outlook 2003 works no sweat under this
configuration, so I am leaning on OL2007B2 having a problem with VPN
tunnels.
Anyone else test OL2007B2 through their VPN client?

J. Merrill
MCP, CCA, NET+
www.gomerrill.com

How are the serverside security settings? It could be configured to
only
allow networktraffic from specified applications.
Another one; what version of Exchange is running? Outlook 2007 cannot
connect to Exchange 5.5 and previous.

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003
http://www.howto-outlook.com/
Outlook FAQ, HowTo, Downloads, Add-Ins and more

-----
in
message Ok, here is the setup:

Laptop w/ Windows XP SP2 + All patches. Running clean Office 2007 B2.

Not connected to the LAN, through a cable modem with Netscreen client
version 8.7:

Fired up Outlook 2007, setup profile, do a manual configure, select
"exchange", then type in server name and mailbox name, clikc on
"Check"...
gets an error:

An unknown error occurred, error code: 0x90040605

If I connect to the LAN, works. If I connecct wirelessly, works.

Ok, so once connected to the LAN and get it to recognize the mailbox
and
get
Outlook configured properly, I am now remote. Connect VPN through
Netscreen
client. Fireup Outlook... It can never connect to the exchange
server.

Frustrated, I uninstall Office 2007 Beta, go back to Office 2003 Pro,
set
it
all up and all works through the VPN flawlessly. Including setting up
Outlook profiles and such.

So, it seems Outlook 2007B2 is having a problem with VPN connections.
We
tested this with the Cisco VPN client and is having the same problem
there,
too. When you look at traffic on the PC, it doesn't even try to send
it
out
the VPN tunnel.

Any ideas? Very strange, as Outlook 2003 didn't care what connection
you
had it on, as long as it had a connection.

Jonathan Merrill
MCP, CCA, NET+
www.gomerrill.com

 

[Guest]

Appreciate your help.

Looking at the sniffer traffic between the subnets, it appears the laptop is
not sending any traffic to the exchange box other than the usual NETBIOS
stuff. Upon hitting "Check" when setting up the profile to looking up a
mailbox, you'd normally see a bit of activity. In this case, tested with
three VPN clients on two different laptops (Dell Latitude D600 and HP Compaq
nc6220 laptop) all running Windows XP SP2 (Build
2600.xpsp_sp2_gdr.050301-1519 : Service Pack 2). None of these test laptops
run the XP firewall. No activity across the tunnel from Outlook.

I can ping the exchange server, I can browse files across the tunnel, and
can web browse our intranet. I can open up OWA across the tunnel.

Thanks again,

Jonathan Merrill
MCP, CCA, NET+
www.gomerrill.com

Can you see at what point they are being dropped? Client level or later? No
clientside firewall that could block the traffic?
VPN to an Exchange server on the same network as an Outlook 2007B2 client
has been verified to work. Still waiting for results for when they are not
on the same network.

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003


-----
message No, not possible. But the curious portion is why Outlook 2003 works
unhindered. This issue only presents itself with OL2007B2.

Also, we are running a sniffer and do not see any packets coming from the
laptop to the exchange server, beyond the usual traffic.

Jonathan Merrill
MCP, CCA, NET+
www.gomerrill.com

Is it possible for you to test it with the same subnet?
Do you see Kerberos packets being dropped somewhere?
What happens when you switch authentication to use NTLM instead?

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003
http://www.howto-outlook.com/
Outlook FAQ, HowTo, Downloads, Add-Ins and more

-----
message No, the VPN connection is on another non-routable subnet. This allows us
to
log any traffic on that particular subnet coming into our test network.

So, the VPN user subnet would be on a 172.16.x.x.
The test server network is 192.168.x.x.

Also, tested this scenario with the Watchguard VPN client, and it also
does
not work.

Appreciate it!

Jonathan Merrill
MCP, CCA, NET+
www.gomerrill.com

Can't test this myself as I currently do not have the setup for it but
I've
passed it through.

As an additional question; is the VPN client located on the same subnet
as
the Exchange server?

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003
http://www.howto-outlook.com/
Outlook FAQ, HowTo, Downloads, Add-Ins and more

-----
message How our network is setup is once you VPN, you can access all ports to
any
of
our servers. Further, the mail server is not locked down or has any
security
templates applied to it. This is a test environment.

And we use Exchange 2003, all patches, all service packs.

Appreciate the response. Outlook 2003 works no sweat under this
configuration, so I am leaning on OL2007B2 having a problem with VPN
tunnels.
Anyone else test OL2007B2 through their VPN client?

J. Merrill
MCP, CCA, NET+
www.gomerrill.com

:

How are the serverside security settings? It could be configured to
only
allow networktraffic from specified applications.
Another one; what version of Exchange is running? Outlook 2007 cannot
connect to Exchange 5.5 and previous.

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003
http://www.howto-outlook.com/
Outlook FAQ, HowTo, Downloads, Add-Ins and more

-----
in
message Ok, here is the setup:

Laptop w/ Windows XP SP2 + All patches. Running clean Office 2007 B2.

Not connected to the LAN, through a cable modem with Netscreen client
version 8.7:

Fired up Outlook 2007, setup profile, do a manual configure, select
"exchange", then type in server name and mailbox name, clikc on
"Check"...
gets an error:

An unknown error occurred, error code: 0x90040605

If I connect to the LAN, works. If I connecct wirelessly, works.

Ok, so once connected to the LAN and get it to recognize the mailbox
and
get
Outlook configured properly, I am now remote. Connect VPN through
Netscreen
client. Fireup Outlook... It can never connect to the exchange
server.

Frustrated, I uninstall Office 2007 Beta, go back to Office 2003 Pro,
set
it
all up and all works through the VPN flawlessly. Including setting up
Outlook profiles and such.

So, it seems Outlook 2007B2 is having a problem with VPN connections.
We
tested this with the Cisco VPN client and is having the same problem
there,
too. When you look at traffic on the PC, it doesn't even try to send
it
out
the VPN tunnel.

Any ideas? Very strange, as Outlook 2003 didn't care what connection
you
had it on, as long as it had a connection.

Jonathan Merrill
MCP, CCA, NET+
www.gomerrill.com

 

[Roady [MVP]]

Tried switching authentication to use NTLM already?

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003


-----
message Appreciate your help.

Looking at the sniffer traffic between the subnets, it appears the laptop is
not sending any traffic to the exchange box other than the usual NETBIOS
stuff. Upon hitting "Check" when setting up the profile to looking up a
mailbox, you'd normally see a bit of activity. In this case, tested with
three VPN clients on two different laptops (Dell Latitude D600 and HP Compaq
nc6220 laptop) all running Windows XP SP2 (Build
2600.xpsp_sp2_gdr.050301-1519 : Service Pack 2). None of these test laptops
run the XP firewall. No activity across the tunnel from Outlook.

I can ping the exchange server, I can browse files across the tunnel, and
can web browse our intranet. I can open up OWA across the tunnel.

Thanks again,

Jonathan Merrill
MCP, CCA, NET+
www.gomerrill.com

Can you see at what point they are being dropped? Client level or later?
No
clientside firewall that could block the traffic?
VPN to an Exchange server on the same network as an Outlook 2007B2 client
has been verified to work. Still waiting for results for when they are not
on the same network.

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003


-----
message No, not possible. But the curious portion is why Outlook 2003 works
unhindered. This issue only presents itself with OL2007B2.

Also, we are running a sniffer and do not see any packets coming from the
laptop to the exchange server, beyond the usual traffic.

Jonathan Merrill
MCP, CCA, NET+
www.gomerrill.com

Is it possible for you to test it with the same subnet?
Do you see Kerberos packets being dropped somewhere?
What happens when you switch authentication to use NTLM instead?

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003
http://www.howto-outlook.com/
Outlook FAQ, HowTo, Downloads, Add-Ins and more

-----
message No, the VPN connection is on another non-routable subnet. This allows
us
to
log any traffic on that particular subnet coming into our test network.

So, the VPN user subnet would be on a 172.16.x.x.
The test server network is 192.168.x.x.

Also, tested this scenario with the Watchguard VPN client, and it also
does
not work.

Appreciate it!

Jonathan Merrill
MCP, CCA, NET+
www.gomerrill.com

Can't test this myself as I currently do not have the setup for it but
I've
passed it through.

As an additional question; is the VPN client located on the same
subnet
as
the Exchange server?

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003
http://www.howto-outlook.com/
Outlook FAQ, HowTo, Downloads, Add-Ins and more

-----
in
message How our network is setup is once you VPN, you can access all ports to
any
of
our servers. Further, the mail server is not locked down or has any
security
templates applied to it. This is a test environment.

And we use Exchange 2003, all patches, all service packs.

Appreciate the response. Outlook 2003 works no sweat under this
configuration, so I am leaning on OL2007B2 having a problem with VPN
tunnels.
Anyone else test OL2007B2 through their VPN client?

J. Merrill
MCP, CCA, NET+
www.gomerrill.com

:

How are the serverside security settings? It could be configured to
only
allow networktraffic from specified applications.
Another one; what version of Exchange is running? Outlook 2007
cannot
connect to Exchange 5.5 and previous.

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003
http://www.howto-outlook.com/
Outlook FAQ, HowTo, Downloads, Add-Ins and more

-----
in
message Ok, here is the setup:

Laptop w/ Windows XP SP2 + All patches. Running clean Office 2007
B2.

Not connected to the LAN, through a cable modem with Netscreen
client
version 8.7:

Fired up Outlook 2007, setup profile, do a manual configure, select
"exchange", then type in server name and mailbox name, clikc on
"Check"...
gets an error:

An unknown error occurred, error code: 0x90040605

If I connect to the LAN, works. If I connecct wirelessly, works.

Ok, so once connected to the LAN and get it to recognize the mailbox
and
get
Outlook configured properly, I am now remote. Connect VPN through
Netscreen
client. Fireup Outlook... It can never connect to the exchange
server.

Frustrated, I uninstall Office 2007 Beta, go back to Office 2003
Pro,
set
it
all up and all works through the VPN flawlessly. Including setting
up
Outlook profiles and such.

So, it seems Outlook 2007B2 is having a problem with VPN
connections.
We
tested this with the Cisco VPN client and is having the same problem
there,
too. When you look at traffic on the PC, it doesn't even try to
send
it
out
the VPN tunnel.

Any ideas? Very strange, as Outlook 2003 didn't care what
connection
you
had it on, as long as it had a connection.

Jonathan Merrill
MCP, CCA, NET+
www.gomerrill.com

 

[Roady [MVP]]

Also note that Outlook relies on DNS for name resolving; not WINS. Can you
ping and access the server by its FQDN? When you ping by Netbios name it
should also return the FQDN of the server otherwise name resolving was done
by WINS and not DNS.

Also use the RPCPing utility to test connectivity.

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003


-----
message Tried switching authentication to use NTLM already?

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003


-----
message Appreciate your help.

Looking at the sniffer traffic between the subnets, it appears the laptop is
not sending any traffic to the exchange box other than the usual NETBIOS
stuff. Upon hitting "Check" when setting up the profile to looking up a
mailbox, you'd normally see a bit of activity. In this case, tested with
three VPN clients on two different laptops (Dell Latitude D600 and HP Compaq
nc6220 laptop) all running Windows XP SP2 (Build
2600.xpsp_sp2_gdr.050301-1519 : Service Pack 2). None of these test laptops
run the XP firewall. No activity across the tunnel from Outlook.

I can ping the exchange server, I can browse files across the tunnel, and
can web browse our intranet. I can open up OWA across the tunnel.

Thanks again,

Jonathan Merrill
MCP, CCA, NET+
www.gomerrill.com

Can you see at what point they are being dropped? Client level or later?
No
clientside firewall that could block the traffic?
VPN to an Exchange server on the same network as an Outlook 2007B2 client
has been verified to work. Still waiting for results for when they are not
on the same network.

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003


-----
message No, not possible. But the curious portion is why Outlook 2003 works
unhindered. This issue only presents itself with OL2007B2.

Also, we are running a sniffer and do not see any packets coming from the
laptop to the exchange server, beyond the usual traffic.

Jonathan Merrill
MCP, CCA, NET+
www.gomerrill.com

Is it possible for you to test it with the same subnet?
Do you see Kerberos packets being dropped somewhere?
What happens when you switch authentication to use NTLM instead?

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003
http://www.howto-outlook.com/
Outlook FAQ, HowTo, Downloads, Add-Ins and more

-----
message No, the VPN connection is on another non-routable subnet. This allows
us
to
log any traffic on that particular subnet coming into our test network.

So, the VPN user subnet would be on a 172.16.x.x.
The test server network is 192.168.x.x.

Also, tested this scenario with the Watchguard VPN client, and it also
does
not work.

Appreciate it!

Jonathan Merrill
MCP, CCA, NET+
www.gomerrill.com

Can't test this myself as I currently do not have the setup for it but
I've
passed it through.

As an additional question; is the VPN client located on the same
subnet
as
the Exchange server?

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003
http://www.howto-outlook.com/
Outlook FAQ, HowTo, Downloads, Add-Ins and more

-----
in
message How our network is setup is once you VPN, you can access all ports to
any
of
our servers. Further, the mail server is not locked down or has any
security
templates applied to it. This is a test environment.

And we use Exchange 2003, all patches, all service packs.

Appreciate the response. Outlook 2003 works no sweat under this
configuration, so I am leaning on OL2007B2 having a problem with VPN
tunnels.
Anyone else test OL2007B2 through their VPN client?

J. Merrill
MCP, CCA, NET+
www.gomerrill.com

:

How are the serverside security settings? It could be configured to
only
allow networktraffic from specified applications.
Another one; what version of Exchange is running? Outlook 2007
cannot
connect to Exchange 5.5 and previous.

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003
http://www.howto-outlook.com/
Outlook FAQ, HowTo, Downloads, Add-Ins and more

-----
in
message Ok, here is the setup:

Laptop w/ Windows XP SP2 + All patches. Running clean Office 2007
B2.

Not connected to the LAN, through a cable modem with Netscreen
client
version 8.7:

Fired up Outlook 2007, setup profile, do a manual configure, select
"exchange", then type in server name and mailbox name, clikc on
"Check"...
gets an error:

An unknown error occurred, error code: 0x90040605

If I connect to the LAN, works. If I connecct wirelessly, works.

Ok, so once connected to the LAN and get it to recognize the mailbox
and
get
Outlook configured properly, I am now remote. Connect VPN through
Netscreen
client. Fireup Outlook... It can never connect to the exchange
server.

Frustrated, I uninstall Office 2007 Beta, go back to Office 2003
Pro,
set
it
all up and all works through the VPN flawlessly. Including setting
up
Outlook profiles and such.

So, it seems Outlook 2007B2 is having a problem with VPN
connections.
We
tested this with the Cisco VPN client and is having the same problem
there,
too. When you look at traffic on the PC, it doesn't even try to
send
it
out
the VPN tunnel.

Any ideas? Very strange, as Outlook 2003 didn't care what
connection
you
had it on, as long as it had a connection.

Jonathan Merrill
MCP, CCA, NET+
www.gomerrill.com

 

[G]

I don't really have an answer to your problem, but I can confirm that
Outlook 2007 B2 works fine over a VPN. The only difference being that I
am not using a Third Party VPN Client. I am using Windows DUN for my
VPN connections. I have about 5 users logging in over the VPN with
OL2k7b2 without a hitch.



=?Utf-8?B?Sm9uYXRoYW4gTWVycmlsbA==?=

No, the VPN connection is on another non-routable subnet. This allows
us to log any traffic on that particular subnet coming into our test
network.

So, the VPN user subnet would be on a 172.16.x.x.
The test server network is 192.168.x.x.

Also, tested this scenario with the Watchguard VPN client, and it also
does not work.

Appreciate it!

Jonathan Merrill
MCP, CCA, NET+
www.gomerrill.com

Can't test this myself as I currently do not have the setup for it
but I've passed it through.

As an additional question; is the VPN client located on the same
subnet as the Exchange server?

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003


-----
in message How our network is setup is once you VPN, you can access all ports to
any of our servers. Further, the mail server is not locked down or
has any security
templates applied to it. This is a test environment.

And we use Exchange 2003, all patches, all service packs.

Appreciate the response. Outlook 2003 works no sweat under this
configuration, so I am leaning on OL2007B2 having a problem with VPN
tunnels.
Anyone else test OL2007B2 through their VPN client?

J. Merrill
MCP, CCA, NET+
www.gomerrill.com

How are the serverside security settings? It could be configured to
only allow networktraffic from specified applications.
Another one; what version of Exchange is running? Outlook 2007
cannot
connect to Exchange 5.5 and previous.

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003
http://www.howto-outlook.com/
Outlook FAQ, HowTo, Downloads, Add-Ins and more

-----
"Jonathan Merrill" <[email protected]>
wrote in message
Ok, here
is the setup:

Laptop w/ Windows XP SP2 + All patches. Running clean Office 2007
B2.

Not connected to the LAN, through a cable modem with Netscreen
client version 8.7:

Fired up Outlook 2007, setup profile, do a manual configure, select
"exchange", then type in server name and mailbox name, clikc on
"Check"... gets an error:

An unknown error occurred, error code: 0x90040605

If I connect to the LAN, works. If I connecct wirelessly, works.

Ok, so once connected to the LAN and get it to recognize the
mailbox and get
Outlook configured properly, I am now remote. Connect VPN through
Netscreen
client. Fireup Outlook... It can never connect to the exchange
server.

Frustrated, I uninstall Office 2007 Beta, go back to Office 2003
Pro, set it
all up and all works through the VPN flawlessly. Including setting
up Outlook profiles and such.

So, it seems Outlook 2007B2 is having a problem with VPN
connections. We tested this with the Cisco VPN client and is
having the same problem there,
too. When you look at traffic on the PC, it doesn't even try to
send it out
the VPN tunnel.

Any ideas? Very strange, as Outlook 2003 didn't care what
connection you had it on, as long as it had a connection.

Jonathan Merrill
MCP, CCA, NET+
www.gomerrill.com

 

[Guest]

I too am having this same problem. I don't have much flexibility in changing
the environment for testing, but I am trying to create a profile while using
VPN and I get the 0x90040605 error. I would be interested in any
workarounds/solutions.