OWA Shows correct Graphics internally, but Not Externally

Exchange 2003 Standard on Server 2003 SP1

OWA works brilliantly from inside.  After several calls to our Provider and Firewall Admin, got things working outside.  To a certain extent.  I can authenticate by going to http://server.domain.com/exchange and it accepts my credentials, but the graphics don't load up.   I get what others have described as the boxes with the x's down the left and no emails loading up.  I searched around but couldn't find anyone who had it working inside, but not outside.  

Any ideas?  Thanks,
Who is Participating?
It usually works everywhere or not at all.

The boxes down the side is usually an indication that the content isn't loading correctly from the /exchweb virtual folder. As it works internally the first place I would look is the firewall.

may be the pictures are not getting loaded, try right clicking on the "x" and select show picture

NDRIAdminAuthor Commented:
Ports 80, 110, 443 are opened on the firewall to the exchange server.  

What else could the firewall be doing to keep my images from loading?  
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Blocking it, scanning it. Any number of things.
You have to look at what is different between an internal and external connection. The traffic flow, things like that.

Have you made any attempts to "secure" the server? Anything that might be restricting access to local IP addresses?

NDRIAdminAuthor Commented:
I havent found anything on the firewall that looks like its blocking anything.  I found another  question on this site that referenced article


It suggested granting authenticated users permissions to the exchweb folder.  Which I have done.  Unfortunately I have no way of testing this while here in the office.  It works here, but not outside.  I'll have to wait until I get home.  Will keep you posted.

NDRIAdminAuthor Commented:
FOrgot to mention.  The article also suggested checking the folders in the virtual directory for Exchweb.  

Verify that the following virtual directories are located in Exchweb: • Bin
• Cabs
• Controls
• Help
• Img
• Views

I have those, but the cabs folder isnt in the exchweb folder.  In exchweb, I also have a folder called 6.5.6944.0, which has a cabs and controls folder in it.  Is this okay?   Thanks again
It works inside - you said so yourself.
Therefore there is nothing wrong with OWA.

Check the authentication settings on the Exchange virtual folders...

/exchange :  basic and integrated only
/exadmin: integrated only
/exchweb: anonymous ONLY
/public: basic and integrated only.

NDRIAdminAuthor Commented:
All of my settings already match what you've laid out.  adding authenticated users to the exchweb folder didn't help.  I don't read firewalls well.   Here is my config.  Not shown, are the ports 80, 443, and 110 to my exchange server.  

NDRI-PIX# sho run
: Saved
PIX Version 6.3(3)
interface ethernet0 100full
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password
hostname XXXX-PIX
domain-name xxxx.com
fixup protocol dns maximum-length 1024
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
access-list MS permit ip host
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside
ip address inside
ip audit info action alarm
ip audit attack action alarm
pdm history enable
arp timeout 14400
global (outside) 1
nat (inside) 1 0 0
static (inside,outside) netmask 0 0
static (inside,outside) netmask 0 0
conduit permit tcp host eq smtp any
conduit permit tcp host eq pop3 any
conduit permit tcp host eq ldap any
route outside 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server RADIUS protocol radius
aaa-server LOCAL protocol local
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
sysopt connection permit-ipsec
crypto ipsec transform-set NORMAL esp-des esp-md5-hmac
crypto dynamic-map 20 11 set transform-set NORMAL
crypto map MANAGED 10 ipsec-isakmp
crypto map MANAGED 10 match address MS
crypto map MANAGED 10 set peer
crypto map MANAGED 10 set transform-set NORMAL
crypto map MANAGED 20 ipsec-isakmp dynamic 20
crypto map MANAGED interface outside
isakmp enable outside
isakmp key ******** address netmask
isakmp identity address
isakmp keepalive 10 5
isakmp nat-traversal 20
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption des
isakmp policy 10 hash md5
isakmp policy 10 group 1
isakmp policy 10 lifetime 86400
isakmp policy 20 authentication pre-share
isakmp policy 20 encryption des
isakmp policy 20 hash md5
isakmp policy 20 group 2
isakmp policy 20 lifetime 86400
telnet outside
telnet outside
telnet inside
telnet timeout 30
ssh outside
ssh outside
ssh outside
ssh timeout 30
management-access inside
console timeout 5
terminal width 80
: end

Gee I hope it's not dangerous to post this.
The PIX doesn't cause these problems.
However you have used Conduits, which are depreciated. The modern format is Access Lists. Did you set that by hand or use PDM?

NDRIAdminAuthor Commented:
Our Provider manages the Firewall.  I make requests for changes.  I'm still boozled on whats wrong.  
It could be something further upstream.
Have you asked the ISP if they are likely to be filtering anything?

As an internal test, create a new local account on a machine that doesn't match any username or password you have in your domain. Then login to that account and see if OWA loads correctly inside on that non-domain account.

NDRIAdminAuthor Commented:
OWA did load correctly internally logged into a pc using a local account, then using a domain account for the OWA log in.  I'll check with the ISP but I doubt they're filtering anything.   I'll get back as soon as I have more answers.  Thanks,

The fact that a local account works rules out authentication as being the problem. I had a though that it could be something in that area.

NDRIAdminAuthor Commented:
Its working now.  It seems that removing the smtp fixup protocol from the PIX did the trick.  Eithe that or it was a huge coincidence.  Though I changed nothing else.  Thanks

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.