Coupee46
asked on
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..
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..
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\driver
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
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\driver
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
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.
ASKER
Thanks for the replies.. I'll take a look at the host and DNS today and let you know.
ASKER
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.
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.
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!
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!
ASKER
Great, thank you diverseit and all others. I'll let you know as soon as I get a chance back on the workstation.
Any update on this up?
Waiting for author reply...
ASKER
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..
OK, thanks for the update. I hope everything personally & otherwise gets sorted out soon for you.
ASKER
Sorry guys.. still haven't had a chance to test the suggestions.. :/ hoping to do so sometime this week.. thanks again.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks!
Hi Coupee46,
What ended up being the solution here?
What ended up being the solution here?
ASKER
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.. :)
I see, thanks for the update.
ASKER
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.