How to connect Windows XP Home to Exchange Server
At our home office we have an Exchange Server 5.5. Now, I want some people from outside to connect our Exchange Server by a VPN system. The VPN is also working fine without any problems but outlook client is not able to connect to our Exchange server. The only difference is that the client is on Windows XP Home, so I doubt that it can be a problem. What can I do to resolve this issue. Thanks for any help.
Re: How to connect Windows XP Home to Exchange Server
I had the same problem. What seemed to fix was to make sure that the Machine name of the XP PC was one recognised by the Exchange Server. Hence, if you are known as WXYZ to the Exchange Server, I found that I needed to give the XP the name WXYZ-PPP.
Also I had to have the domain settings correct on the Exchange Server login. But this alone did not work without giving the XP PC a recognisable name.
Re: How to connect Windows XP Home to Exchange Server
You can also create a batch file to connect Windows XP Home to Exchange Server. Since this is home PC what you are expecting from Outlook, is not possible. You will have to enter password everytime.
For Share you can create a .bat file and put this line in it.
NET USE J: \\yourservername\sharename /USER:yourdomainname\theusername thepassword
Once Batch file is created, place it in the startup folder.
Hope this helps
Re: How to connect Windows XP Home to Exchange Server
Try disabling Exchange cache mode.
Remember that you are using the network connection to the remote desktop which is the same network connection used to connect to the Exchange server. Could be you are simply flooding your NIC with so much traffic that delays are incurred for Outlook on the remote host trying to get at the Exchange server.
I don't know how well RDP handles graphical data, like your desktop. If it attempts to transmit the entire screen to reflect a single pixel change, that's a hell of a lot of traffic. I know that some versions of VNC will only send incremental screen changes to reduce traffic size. You might want to try TightVNC instead of RDP.