Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

Home Office Client not receiving mail from internal clients

Posted on 2006-11-06
6
Medium Priority
?
216 Views
Last Modified: 2010-03-06
Hi There,
This is Windows SBS 2003 Exchange Server I am speaking of, but thought it is a pure exchange issue not really an SBS, please ask me to move it if neccc

I have an office of 7 people, two of which work from home offices.  They are not recieving mail sent to them from the internal clients.

They have network logins and exchange emails, but never connect to the network.

Our website is hosted by LDMI, as is the email.

Each user has a pop email setup on thier system, including the home users. Everyone gets and sends emails to others no problem save the above.

In active directory Users and Computers, I tried taking out the local address for the home users, so that just thier external smtp address was left, and it was made primary.  This made no difference...

Wondering if I should just delete thier local accounts and would that solve the issue.  Neither needs to really logon at the office, at least not with email capability.

I do not have the pop connector enabled.

Please help, I could really use to solve this by tomorrow.

Dave
0
Comment
Question by:knowseeker
  • 3
4 Comments
 
LVL 39

Expert Comment

by:redseatechnologies
ID: 17885708
Hi knowseeker,

The problem is going to be that you are trying to send mail OUT that the server knows it is responsible for.

Ideally, you should stop having your mail hosted externally, ditch the horrible pop3 connector, start receiving email directly, and have your remote users on RPC/HTTP

At the very least, getting your remote users on RPC/HTTP would resolve your issue

http://www.amset.info/exchange/rpc-http.asp

Hope that helps,

-red
0
 

Author Comment

by:knowseeker
ID: 17891112
Actually, I'm not using the pop3 connector.   I realize that that the server thinks it should keep the email, just seems like I should be able to tell it no....

_ Would deleting thier user accounts be the quick way to resolve the issue?_

would like to stop having email hosted externally, but like the idea if thier server goes down, email is still stored somewhere until it comes back up...  

will look at the URL you provided, thanks, and please respond to the above if possible.  Ok, I looked at that, and it sounds like the ideal scenario.  The problem is, I need a solution I can implement in an hour, and that is not the case there.  Both outside users are used to being outside, and they can stay that way for now.  I can see that this would allow them full network access, and is the best solution, but it needs  to wait for now...

Yours,
Dave
0
 
LVL 39

Accepted Solution

by:
redseatechnologies earned 2000 total points
ID: 17892858
> I can see that this would allow them full network access

No it wouldn't, all you need to do is open port 443 and they will be able to open their mail directly.

> The problem is, I need a solution I can implement in an hour

Implementing RPC/HTTP would take little time, assuming you followed the above guide PERFECTLY (that includes testing time).  Once you have tested it and know it works, you can send your users to http://www.amset.info/exchange/rpc-http-client2.asp

> _ Would deleting thier user accounts be the quick way to resolve the issue?_

I should have answered that.  No, it won't.  The problem is that your server thinks it is responsible for ALL mail on that domain.  There are ways around this, but none of them are pretty (especially compared to RPC/HTTP).  One quick solution would be to get the POP3 accounts elsewhere and forward their domain mail there (you could even use GMAIL for that).

> would like to stop having email hosted externally, but like the idea if thier server goes down, email is still stored somewhere until it comes back up...  

Email will keep trying to come through for 48 hours, if your server is down longer than that, you have bigger problems than lost mail.

-red
0
 
LVL 39

Expert Comment

by:redseatechnologies
ID: 17892887
Here is a way to have 2 servers responsible for the domain (which would fix your issue, but look how much messing around it is)

http://www.amset.info/exchange/twositesonedomain.asp

RPC/HTTP is your best option - if you have OWA working already, you are half way there.  If you have a purchased SSL certificate already installed on the server, you have done the hard part.

-red
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Eseutil Hard Recovery is part of exchange tool and ensures Exchange mailbox data recovery when mailbox gets corrupt due to some problem on Exchange server.
This article will help to fix the below errors for MS Exchange Server 2016 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…
Suggested Courses

581 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question