I have remote users who are not allowed on the domain...
At times they need to work in the main office and log in via wireless directly to the Wirelss ADSL modem/router.. putting them in a different ip range to the domain. Internet access works well with this arrangement but they are unable to get to the company mail server on the SBS2003 server the modem also attaches to via its own NIC.. The mail server can be pinged sucsessfully .. but the MS error says it could be an SSL error. I was hoping that would go out to the web and back to get the mail but it is being blocked. Access to Remote Web Workplace is also blocked in this same situation. Do I need so specific filtering setup to handle this? Or is there some other method around the problem? Thanks for any assistance
Software/Hardware used:
ASKED:
November 29, 2006 4:19 AM
UPDATED:
November 30, 2006 9:38 AM
I assume these people are trying to connect via Outlook Web Access or POP3 and that they can normally do so from elsewhere.
Take a look at your Exchange machine. Are the wireless IP ranges allowed to connect to the OWA Web Server? I think that is the directory security page. Check all the places in Exchange where you can restrict/authorize service via IPs for OWA and POP3.
Finally check the firewall settings both on your dedicated (hardware) firewall and on Exchange. Are the HTTP/POP3 and SSL ports open for the wireless IP range?
More information on how the users normally connect to the exchange server would be most helpful here. Each of the various methods has its pluses and minuses and little tricks depending upon the situation.
You really need to provide more information.
When you ping the SBS from the wireless, does it by IP AND by name? Since we don?t have a lot of information, to be simple, ping by IP shows connectivity; ping by NAME show name resolution.
How do they connect to obtain their email while on the outside? If you have RPC over HTTP then it should work regardless of where they are working. If they are using Outlook Web Access, then it could be name resolution and you will have to adjust your internal DNS, might be as simple as placing a host record for example mail with the internal IP address.
If you will provide greater detail, it would help us in trying to assist you with the correct path to try.
Best of luck
dmw