Search results for query: *

I understand the need for the front-end solution, but I also like the idea of installing OWA on the web server. There will be only about 5 OWA users and probably only 2 of those will use it even once a day. So I don't figure bandwidth will be a problem. I wasn't aware you could install just...

If you choose to expose you Exchange backend server to the Internet, all that is required for OWA to work is to have port 80 open. I can do this by changing the firewall settings so that port 80 is open to the Exchange server instead of our webserver (of course this makes our website...

In our firewall, I can direct port 80 to the IP of the Exchange 2003 server and OWA is avaliable externally. The problem is, we normally have port 80 directed to our web server. I tried directing port 80 to both IPs by making an entry for each and also by directing to a range that contained...

Thanks Marc!! It seems that all my public folders are mail-enabled already. Indeed, internal users can send email and it lands in the proper public folder. So, I set POPCon to check the "feedback" account at the ISP and deliver it to the "feedback" public folder. For some reason, it will not...

I have an odd requirement: Our email is hosted by our ISP, and we use a POP3 connector to periodically bring it into our Exchange Server (2003). One of these email accounts does not correspond to an actual user (feedback@ourdomain.com). We want all email addressed to feedback@ourdomain.com to...

Slight correction. This happens SOMETIMES. Evidently it is intermittent for any given user.

We are running W2k3 Server SP1 for our domain controller. We are running W2k3 Server SP1 on our exchange server. Workstations are running XP Pro and Outlook for mail client. Users log in to the domain, but the first time they open Outlook, it prompts them to autheticate against the domain again...

Awesome! Thanks all of you!

Thanks for the feedback. Actually I was logged in to both computers as the Domain admin, and that account has Exchange Full Administrative rights. There may be some other setting that I could have to make the options appear on the domain controller, but as long as nothing is "broken" with the...

After installing our first Exchange Server 2003 on new hardware, I can start "Active Directory Users and Computers" on that machine. When I right-click on a user, I see "Exchange Tasks..." listed. When I look at the properties of a user, I see all the tabs related to Exchange. If I start...

I've got a W2k3 Server (A) which is the domain controller (name of domain is "XXX" for instance). I've got another W2k3 Server (B) (no roles yet) which is on the network as a member of a workgroup. When browsing the network in Windows Explorer from Server B, I can see all the domains and when...

Thanks to both of you! That is very helpful and gets me on the right track. I had tried to find something in the MS knowledge base on this, but no matter how I designed my searches, there were no results that were relevant.

We have: server1 - W2k3 Server, which is the Domain Controller server2 - W2k3 Server, which has Exchange 2003 Server clients - Win XP, which use Outlook as the mail client We want to replace the hardware for the Exchange server. No software or configuration changes at all. What is the best...

I have also had this problem with the Outlook clients for some time. Our users often address emails to both internal and external addresses. As long as the mail is sent via the POP account, everybody gets it since our internal email addresses are the same as our external ones (ex...

I'll look into the POP3 connector. If I can make that work (at least for a few months) then that would be a big help. Thanks!

Is it possible to have Exchange Server 2003 check external POP email accounts on the Internet and then relay those emails to the correct internal user?

In another thread I posted a question about how to go about hosting your own email. I got some good feedback, but now I'm curious as to what people think about it being recommended or not. Here are my two options: 1) Use Exchange Server 2003 on our network to provide our users with public...

Thanks Ken for the advice. That is the direction I'd like to go in for setting this up. We used an old version of SBS and it caused so many headaches that we decided not to go further with it. Since we have already purchased W2k3 and Exchange 2003, we are committed to them even if it turns out...

Thanks Zelandakh for the fast response! I inherited this mess and have been keeping it afloat for a while, but I would like to set up the new network in a more proper way. Unfortunately, I'm out of my depth here so forgive me for the follow-up questions. I pretty much understand that the...

In our small company we run Win NT 4 and Exchange 5.5 for internal email and have external email hosted through an ISP. The ISP also hosts our domain name. Our network domain is the same name as our public domain name (ex. mycompany). Each workstation on our network has Outlook set up to...