vpn and outlook issue

solvent · 14-10-2008

I have a laptop running XP SP2 with Outlook 2k3. I've setup a VPN client connection on my laptop. When I connects to the VPN, it says it's connected but Outlook won't connect to the Exchange server. What would be causing this problem? Any help would be greatly appreciated.
thanks,

**Spyrus** · 14-10-2008

Once he connect, can he ping the IP address or name of the other client machine or exchange server? Can he access things other than Terminal Services on the remote network?

He can probably ping machines on the remote network. I think he has some other problem. Maybe a firewall issue.

**Trojan123** · 14-10-2008

Make sure the VPN isn't restricting the port? Can it ping the server?

**Steve123** · 14-10-2008

Can it connect via OWA (Outlook Web Access) after Outlook dies? Just wondering, not sure if its relevant. VPN connections normally don't die without some errors at one of the endpoints.

Is each machine doing a separate VPN or are you tunneling?

Yogesh · 14-10-2008

Exchange server has a Broadcom Net Extreme II NIC card. This seems like an odd fix since only one user has the problem. Exchange by default has some new TCP/IP features enabled. Older NIC drivers aren’t compatible with these features, so you need to update your drivers to solve the issue. Basically none other than M$ (Microsoft), assumed with their latest version of Exchange that the server’s NIC card has the latest drivers. If the server doesn’t, there are some new TCP/IP features Exchange has enabled that may cause problems. Due to this Some Outlook clients may be unable to connect to Exchange.

Broadcom has provided an update to their drivers that helps resolves the issues with these offloading feature problems. To determine if you have the correct update, you need to check the version numbers to ensure they are 3.7.19 or later. Anything lower than that does not have the fixes in them.

For solution, refer this link The Microsoft Exchange Team Blog.

I think there are a few issues though that may have caused this problem for the one particular user. With the primary one being he is a new user. Beyond that I am not really sure what else could have caused this to happen.