Well, I finally got Exchange Server 2000 to work on the new Windows 2000 Server. It was a lot of work, and I needed Microsoft's Technical Support to get it done, but it is now done. Now, I've got an old problem, which the former system admin fixed years ago, but I don't know how to fix. Basically, what is happening is that we cannot send any outbound email (email meant to be sent to some email address outside of our network). Any email within our network works fine. Any email that comes from an external source but is sent to someone within our network works fine. But any email that anyone within our network attempts to send outside of our network, doesn't work at all. We are getting "Delivery Status Notification (Delay)" messages a few hours after attempting to send an email to some external address. However, in a sense, this hasn't ever worked quite right, although it has worked. Let me explain. Our network is "amci.unm.edu". For argument's sake, if I had an account at work called "Rod", then to log into my account I could use rod@xxxxxxxxxxxx for the account (profile) name, and then my password. However, we have never used such email addresses to send email to anyone outside of our network. Instead, we have used the email addresses that were assigned to us by our ISP, which in this case is the University of New Mexico (for argument's sake I'll call it rod@xxxxxxxx) But, for years, we have been able to successfully send and receive emails from external sources just fine. My former boss set us up in Exchange, somehow, so that any outbound email would go into a queue in Exchange and eventually through our ISP to the outside world. I probably should just leave it that way and do whatever fix he did, in order to be able to send email to the outside world, and still use the internal email addresses for internal correspondence/collaboration/etc. So, how do I do that? Alternatively, I guess it would be possible to actually make it so that email addresses like rod@xxxxxxxxxxxx would work, but I haven't a clue as to how I would go about making that possible. How does one do that, if one wanted to? Rod ******************************************************** This Week's Sponsor - RTO Software / TScale What's keeping you from getting more from your terminal servers? Did you know, in most cases, CPU Utilization IS NOT the single biggest constraint to scaling up?! Get this free white paper to understand the real constraints & how to overcome them. SAVE MONEY by scaling-up rather than buying more servers. http://www.rtosoft.com/Enter.asp?ID=147 ********************************************************** To Unsubscribe, set digest or vacation mode or view archives use the below link. http://thethin.net/win2000list.cfm