Cannot access Outlook OWA within network

Hello All,

I have another issue that I cant seem to figure out.

A user desktop is on the same network as my desktop and all other users.. The same Subnet/Gateway.

Unfortuantley, I am unable to access our Exchange OWA URL from the users machine.  Everyone else can do so with no issues, but for some reason this user cannot.

-When I attempt to ping owa.xxx.com/owa it comes back request timed out.
-When I ping owa.xxx.com/owa from all other workstations it resolves the internal IP address of the Exchange server

ANy thoughts, suggestions?  We are on a sonicwall firewall router, but there is no rules or restrictions setup..
LVL 1
Coupee46Asked:
Who is Participating?
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.

Coupee46Author Commented:
Here is another wierdness I noticed..

So when pinging OWA internally it should resolve to the Exchange server, but on the users workstation, its attempting to resolve the external IP address.
0
Nick RhodeIT DirectorCommented:
check to see if he has a static entry that is bypassing your DNS server.

If there isn't a static entry navigate to the hostfile, open up in wordpad or notepad and see if there are any entries in there.  

Host file location: C:\Windows\System32\drivers\etc

Should look something like this:

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host

# localhost name resolution is handled within DNS itself.
#      127.0.0.1       localhost
#      ::1             localhost
0
carlmdCommented:
Compare the dns setting on the non working pc with one that works. My guess is that it is pointing to something different for resolution.
0
Increase Security & Decrease Risk with NSPM Tools

Analyst firm, Enterprise Management Associates (EMA) reveals significant benefits to enterprises when using Network Security Policy Management (NSPM) solutions, while organizations without, experienced issues including non standard security policies and failed cloud migrations

Coupee46Author Commented:
Thanks for the replies.. I'll take a look at the host and DNS today and let you know.
0
Coupee46Author Commented:
Diverseit,

nothing comes up under the knowledge base link?  The thing is, all other workstations on the network can access OWA internally with no issues.. its just this one user/workstation.
0
Blue Street TechLast KnightCommented:
Gotcha! On the link...something must be blocking it on your side. I just checked it - it pulls right up.

Regardless, I think your in good hands on where the other experts are leading you.

I'll continue to monitor if your still having issues.

Cheers!
0
Coupee46Author Commented:
Great, thank you diverseit and all others.  I'll let you know as soon as I get a chance back on the workstation.
0
Blue Street TechLast KnightCommented:
Any update on this up?
0
carlmdCommented:
Waiting for author reply...
0
Coupee46Author Commented:
Sorry for delay response.. i had a family emergency and havnet been back in the office lately to follow up. I will keep posted when I do so..
0
Blue Street TechLast KnightCommented:
OK, thanks for the update. I hope everything personally & otherwise gets sorted out soon for you.
0
Coupee46Author Commented:
Sorry guys.. still haven't had a chance to test the suggestions.. :/ hoping to do so sometime this week.. thanks again.
0
Blue Street TechLast KnightCommented:
No problem...I'm still here ready when you are!
0

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
Coupee46Author Commented:
Thanks!
0
Blue Street TechLast KnightCommented:
Hi Coupee46,

What ended up being the solution here?
0
Coupee46Author Commented:
WIndows firewall... Apparently group policy kept enabling Windows Firewall.  I disabled and it looks to be working now.  So far at least, that was the only steps I had tried and it started to work.. :)
0
Blue Street TechLast KnightCommented:
I see, thanks for the update.
0
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.