>Yes the client is connected fine via the VPN, they can
>browse the network and I can run Netstat -na on Exchange
>and see the client's IP address with connections to the
>Exchange server, it just keeps prompting as if the
>password was incorrect. The password is correct, we even
>tried changing it. Still no luck.
>Any other things that may help?????
>>Can the client attach directly to the network and work
>>Is the client receiving DNS information from the same
>server that the
>>Exchange Server and domain controllers are pointed to?
>>And is there ANY filtering on the Cisco?
>>In general, a VPN should perform exactly as the client
>located on the local
>>network, there is no difference. Problems are often
>attributed to incorrect
>>name resolution, filtering, or NAT translations.
>>> We have a client that is connecting via a Cisco VPN
>>> HQ office. The VPN client seems to be working fine, I
>>> ping and resolve the Exchange server and see the
>>> IP on the Exchange server with a NETSTAT command.
>>> when the client opens Outlook XP they are prompted for
>>> username, password & Domain as usual however, they
>>> it once then are prompted a second time, then are
>>> the following error message:
>>> "Your logon information was incorrect. Check your
>>> and domain, then type your password again. If your
>>> is new or if your administrator requested a password
>>> change your will need to click Change Password then
>>> with your new password."
>>> Can anyone help? I have logged on locally to this
>>> and the user can connect fine using OWA, so the
>>> password and domain are fine.
>>> Any help is much appreciated,
>>> Frank Mirecki
>Frank, it sounds like the RPC in the registry is
corrupt. I suspect the XP client updated to SP1 or
Office XP SP1 or 2. To verify if this is the problem,
open the registry (regedit) on the client. Go to
HKEY_local_machine, Software, then to Microsoft then to
RPC and finally to ClientProtocols. On the right you
should have approx 6 string entries. You probably have
2. The ncacn_np for named pipe. That is why you are
getting rejected by the exchange server. Contact me or
Microsoft to get the correct strings if you find they are
missing. Good luck.