Outlook ports through a Linksys router\firewall

[Doug]

I started a new service provider that allows my corporate
VPN to connect to my company. Once inside the VPN, I
cannot connect Outlook to the Exchange server. I can
resolve teh Exchange servers IP address, but Outlook will
not complete the connection although it does try. The
Linksys is a BEFSX41, and is NAT'ing the PC to a private
address 198.168.x.y. When I connect directly to the DSL
modem within the VPN things work fine. What setting can be
chnaged in the router/firewall to enusre that the RPC
calls get routed properly.

Please advise.

 

[Lanwench [MVP - Exchange]]

I started a new service provider that allows my corporate
VPN to connect to my company. Once inside the VPN, I
cannot connect Outlook to the Exchange server. I can
resolve teh Exchange servers IP address, but Outlook will
not complete the connection although it does try. The
Linksys is a BEFSX41, and is NAT'ing the PC to a private
address 198.168.x.y. When I connect directly to the DSL
modem within the VPN things work fine. What setting can be
chnaged in the router/firewall to enusre that the RPC
calls get routed properly.

Hi - this isn't really an Outlook issue as much as a networking one. Have
you tried upgrading the firmware on the Linksys? Can you resolve the
Exchange server's name? If you ping the NetBIOS name, does it reply, or do
you get host unknown? If you add your server's private IP and NetBIOS name
to your PC's hosts file, does it work then? If you can ping it by name, can
you then open the mailbox?

 

[Brian Tillman]

I started a new service provider that allows my corporate
VPN to connect to my company. Once inside the VPN, I
cannot connect Outlook to the Exchange server. I can
resolve teh Exchange servers IP address, but Outlook will
not complete the connection although it does try. The
Linksys is a BEFSX41, and is NAT'ing the PC to a private
address 198.168.x.y. When I connect directly to the DSL
modem within the VPN things work fine. What setting can be
chnaged in the router/firewall to enusre that the RPC
calls get routed properly.

Seems to me this is a known problem with some Linksys routers and the answer
was a firmware update. Google this group for the other conversations about
it.