I just worked around this but would like to learn why things weren't

We use a client-to-site VPN for just about all outside access but, in
to allow access once in a while for someone without the VPN client, we
a couple of NATted addresses. In this case, one of our available
addresses was NATted to 192.168.x.12. The public address shows up
when I do
DISPLAY SECONDARY IPADDRESS, NAT entries look right to me, etc.

The machine could browse the internet just fine but I'm assuming
because browsing is set to go through our 192.168.x.1:8080 proxy.
trying to use Outlook or OE for email, the machine couldn't find the
server and failed every time. Likewise the user couldn't install AOL(company president's wife so she's allowed <smile>) because the setupprogram said it couldn't find an internet connection - that one I find

really strange because even with IPFLT unloaded, it still wouldn't

My initial "fix" was to plug the machine into the public hub and let
it get
a DHCP-supplied address from the router. (Our Netware DHCP server
gives out
192.168 addresses while our router give out 10.x.x.x, very convenient
testing from the public hub.) Then I realized it might be the whole
NAT/static_ip business and let the machine get a DHCP-served address
the usual private-side source and all continued to be well.

The public, non-VPN access isn't something we're still using on a
basis so it's no great loss but I would like to understand what's notworking and why it's not working. Any suggestions for me?

Many thanks in advance.