remote access to exchange server 2000

I'd suspect two things. The first being firewall rules or router ACLs blocking the parts required for MAPI, LDAP, and/or Directory Service access. The second being that the remote office may not be able to resolve the host names they are being refered to by the Exchange Server. Take a look at the following MS KnowledgeBase articles for some additional information: 256976 & 270836.

Hope this helps with the problem.
Cheers!
~Sean

*********************************************
NOTE - When closing your question, please
provide comments. - Thank you.
*********************************************

Since they are part of a different domain (and I mean part of a different Windows NT domain, since that is what I am assuming you mean), then I don't think those clients can connect to Exchange using the "Corporate Workgroup" method.
I could be wrong on this one, but for Corporate Workgroup configuration of Outlook to work to connect to Exchange, the user must be logged into their workstation with the same NT username/password that their mailbox is associated with. That is how a normal user onthe LAN can just log into their NT/2K/XP workstation, open up Outlook, and not be presented with any login box. Their signon information on their workstation is passed to Exchange for verification. This is the single sign-on concept.

Now, since this remote office is on their own Windows domain, then their NT/2K/XP user accounts are not associated with their mailboxes on your Exchange server.

So, I suggests these remote users use POP3 and SMTP to get/send their mail through you. YOu would open up TCP ports 25 & 110 on your firewall to allow access from the remote office to Exchange.

Please post a followup on this issue. I have not been around Exchange for 2 years now (been stuck in Lotus Domino hell!!!!) so I am rusty on Exchange.

Make it simple! Think about firewall or proxy since you site will be communicating over the WAN using public address. NAT (Network Address Translation). What you will have on the outside will be a service provider to ensure that DNS side of things is taken care of. Once your firewall or proxy is configured you will then allow required ports as appropriate. Try the link below to understand basic config.

http://rr.sans.org/encryption/NAT_checkpoint.php

Try to create a VPN connection between the remote office and your office. Route all traffic from the remote office with destination the local lan of your office trough the VPN tunnel, there will not be any problems using the remote domain to log-in and connecting to an exchange trough the tunnel located in an other domein (will get a pwd pop-up).

I don't know what router you're using at the remote office, but make sure it has a VPN server build-in. I'm doing this for many clients and all works fine, we are using draytek routers (able to connect to PIX)

Hi,

your Problem is not simple and E2k functions very different then E5.5. You have to associate the Postbox of the user with an external Account in the Active directory. Since E2k does not have an own Directoryservice like E5.5, you have only one point of account Managment( the AD). This is not very simple, but possible. First you have to create dummy Accounts for the MBX in the AD and referal them as External Accounts to their Postbox in Exchange. It sounds Strange, and it is a little bit Strange but it does work in the way you mention. Look in Technet for external account refereals for E2k MBX, their you find the guide for it.

regards

Frobo

It sounds like a routing and a DNS problem.
1.) Have you added the Exchange server NetBios name to the users hosts file?
2.) Does the DNS on the Exchange Server recognise the computers in the 2 nd office.
3.) Have you tried only connecting the 2 offices, no other internet traffic?

DR