On dialup w/ 3 yahoo email addresses, cannot get from one address to another. Help. Please.

Question

Mozilla Firefox has been shutting down on us, that is true...
But... this evening, my issue may be unrelated to that. I can get to email on two of our three yahoo email accounts, but not the third (not the [email protected] account). (So, if you send me a response to this question at that email address I may not be able to get to it to read it.)
I realize this may be a yahoo issue, not a MF issue but... well... here goes. I sign in to the above email address. The page comes up. I click on Mail. The mail does NOT come up. The page stays white/empty. When I click on the back arrow and get back to the sign-in page I find the email sign-in information is one of the other email accounts in our house. So I delete it and put mine in (again), sign in again and go through the same rigamarole again (and again), unable to get to the inbox and my emails.
Well? What do you think? Can you help? Hope so. Thanks!

Answer 1

A relevant part of your config is missing. On the end there should be the following part:
policy-map global_policy
class inspection_default
  inspect dns preset_dns_map
  inspect ftp
  inspect h323 h225
  inspect h323 ras
  inspect ip-options
  inspect netbios
  inspect rsh
  inspect rtsp
  inspect skinny 
  inspect sqlnet
  inspect sunrpc
  inspect tftp
  inspect sip 
  inspect xdmcp
  inspect icmp       ! <------ Is this line there?
service-policy global_policy global
The line "inspect icmp" is needed to ping through the ASA.
Should the subnets 192.168.2.0/24 and 192.168.3.0/24 go through the ASA to the internet? Then the NAT has to be expanded:
nat (inside) 10 192.168.0.0 255.255.252.0
And now the real challenge:
The ASA should not be the default-gateway for the devices in the 192.168.0.0/24 subnet. That is possible, but makes your network overcomplicated and you will have problems to troubleshoot it.
If you can't separate the ASA with a Layer3-switch from the main network it's best to put the static routes for 192.168.2.0/24 and 192.168.3.0/24 on every device in the 192.1668.0.0/24 network.
The reason for that is that the ASA by default doesn't allow hairpinning where traffic enters and leaves through the same interface (inside in your case). That can be configured, but the ASA is not the device that is designed for that task.