At 18:54 27/02/00 -0500, you wrote:
>At 10:43 PM 2/27/00 +0000, James Lewis wrote:
>
>>I have 3 NT workstations on an internal LAN, going through ipmasq (on
>>2.2.13) which is providing NAT. General services such as web browsing,
>>FTP etc, are working fine but we are experiencing very annoying problems
>>with Microsoft Outlook 2000 (running in 'Corporate Workgroup mode)
>>running on the 'Internal' machines connecting to an External Exchange
>>server with a public IP.
>>
>>The problems seem to be because the exchange server is seeing requests
>>from 3 different machines coming from the single IP address of the NAT
>>machine (the problems more or less go away when there is only one machine
>>running internally). The same problem is arising with Visual Interdev
>>running internally, connecting to an external SQL server.
>>
>>Anyone had the same problem? Is there a way around it, that doesn't
>>involve moving the exchange server to the Internal LAN?
>
>This is peculiar. I have a client who is doing the same thing (well, the
>NAT is being done by a cisco router between internal and external LANs),
>and they have no problems getting to the exchange server. Can you be more
>specific about what the problems are?
>
The Outlook clients, and the Interdev Clients work for a few minutes, then
report constant time outs, or 'Network Unavailable' type errors - (however
other utils such as Internet explorer carry on working fine). Outlook
starts working again after a few retries, and Interdev must be closed and
reopened before it works again.
It seems like ports are being held open, or not closed properly or
something like that - although thats just a random uneducated guess.
