Outlook on Domain computer cannot connect to other shared Exchange Mailbox

I have a few AD users that don't have a need for their own primary Exchange mailbox.  They all currently log into Webmail and use the same one, support@domain.com.  In addition, some users connect via their local NON-domain computer with outlook (HTTPS\RPC) and it works fine.

The issue i have is when attempting to connect outlook on a domain enabled computer to this "shared" exchange account I receive the following error:

"the name cannot be resolved. the name cannot be matched to a name in the address list"

Why would outlook give this error on a domain pc, but a non-domain works great.
dtsheltAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Skyler KincaidNetwork/Systems EngineerCommented:
Are they all using the same wireless/network?

If the non-domain computers are connected to different wireless that is outside the network then you may need to create an A record that points mail.company.com to the internal IP of your mail server.

It is probably struggling to resolve the name internally.

You can also setup the Outlook Anywhere settings even if you are using a domain account under the proxy settings inside the advanced settings when setting up the account.
Adam BrownSr Solutions ArchitectCommented:
You could get this if RPC traffic isn't routing properly internally or if you have a firewall on the system or network that is blocking RPC access to the CAS servers. RPC requires a large number of open ports to function on the internal network, and if the server is configured to use the full port range but there is a network firewall rule blocking some of the RPC port range, it will fail occasionally and unpredictably. Try manually configuring the domain client to use RPC over HTTPS and see if it works. If it does, then you have a networking issue.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Outlook

From novice to tech pro — start learning today.