|
rdouglass -> RE: Odd trouble! (7/25/2007 8:56:33)
|
quote:
There will be any problem with the router! Sorry. Didn't realize you were waiting for another reply. It's not a problem with Cisco routers or any router for that matter. It's just that sometimes with using NAT (Network Address Translation) for accessing "inside" hosts to the outside, the machines on the inside get confused. DNS entries from outside your network are telling browsers that the IP address of the host is on the outside interface of your firewall. Well inside browsers are already inside and then DNS tells them it's an outside IP address. SO the request goes from the inside interface to the outside interface and then back to the inside interface. Now if gets a little busy on the router or other devices on the network aren't very responsive, it can get confused and either drop packets or they start going thru 'loops' of outside/inside/outside/inside/etc. That make any sense? Anyways, if that is the problem you are experiencing the easiest way to fix it is to either put a DNS *inside* your network and have all inside (LAN) users pointing to that DNS. Then add an "A" record for inside hosts to that local DNS. OR put a host entry at the local level pointing to the inside host if you do not have DNS. That help any?
|
|
|
|