This is a limitation of the current NAT reflection implementation. If
this doesn't suit your needs, then you should consider a split-horizon
DNS configuration instead.
Oliver von Bueren wrote:
Chris Buechler wrote:
Trave Harmon wrote:
Now when I telnet the public IP that the 1^st virtual is assigned,
it just sits there and times out. This is making it impossible to
send messages from domain to domain within the network.
It sounds like you're using 1:1 NAT, which means NAT reflection isn't
going to work (it sometimes doesn't work that well anyway).
You need a proper split DNS where internally things resolve to
private IPs.
Hmm, I don't understand your comment. Why should the NAT reflection
not work on a 1:1 NAT? I think this is one of the most used
situations, having a few IP addresses on the WAN interface with 1:1 to
internal machines. That way you don't have to fiddle around with port
forwarding, just with the firewall stuff. You'd need one IP per server
anyway, if you offer the same services on all the internal machines.
Confused...
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
