(ASCEND) BUG in NAT?

[Norbert Wegener <wegener@rw.sni.de>]

In our company we have a central netscape server for an automatic
proxyconfiguration for all Netscapeclients.
This works from any remote site. It works on clients, connected directly
to a Max. It works with every client operating system.
When I use a pipeline with NAT (Even the latest 6.0 Release),
the proxyserver is contacted and also it replys immediately, as tcpdump
shows me. Because the Netscapebrowser does not show any reaction in the
next up to 40(!) seconds, I thought, there might be a fault in the
Natcode, so that the answer from the configserver is not tranlated
correctly. 

Has anyone on the list had the same problem?
May I have an configuration problem? All the other stuff works great
with the pipeline.

Norbert Wegener
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>

---

• Prev by Date: (ASCEND) NAT ??
• Next by Date: (ASCEND) Ascend-Client-Gateway RADIUS attribute?
• Prev by thread: Re: (ASCEND) Ascend-Client-Gateway RADIUS attribute?
• Next by thread: (ASCEND) NAT ??
• Index(es):
  • Main
  • Thread