Similar Threads:
1.Strange conflict between DNS and FTP publications
Hi all,
I've a strange problem I'm not able to clearly identify.
My ISA Server 2000 (running on Windows 2000 AS) is
publishing 2 DNS servers and one FTP server. It was
working fine since few weeks ago, but now has this
problem:
If both DNS and FTP publications are enabled, the 2 DNS
are unreachable. As soon as I disable the FTP
publication, the DNSes start working. If I reenable the
FTP, after a while (maybe 1 hour, maybe 1 day) both DNSes
stop responding again (the still respond from the DMZ,
but not from the Internet).
What maybe the problem ? What should I check ?
I checked all the security bulletin for DoS attacks
regarding DNS or FTP, but found out only patches I'd
already applied.
Nothing special on the logs (or, at least, I don't know
what to look for).
Any help is appreciated.
Thanks.
Massimo.
2.FTP outward traffic causing "Unidentified IP traffic" error on ISA 2004 server connected to a PIX
We have a problem with outgoing FTP traffic going through our ISA 2004
server from one of our remote sites. It works absolutely fine from our
main office, but when the traffic originates from our regional office
(we connect to their Pix router via a VPN), it fails every time. The
error from her workstation is "Windows cannot access this folder. Make
sure you type the file name correctly, and that you have permission to
access the folder. Details: the operation timed out". The user has a
Windows XP PC but Windows firewall is switched off. There is a rule our
firewall to allow access from all our subnets (including those from our
regional office), so this should be applicable to all no matter what
their location, however as a test I created a new rule specifically for
the regional office subnet, which failed. I also started logging on the
ISA server, while the user tried this operation again, and the message
stated that the protocol was 'unidentified IP traffic' and the action
was 'closed connection' (the source network was confired as 'internal
however').
The guy who looks after the PIX is away at the moment, but I was
informed by others that it is not configured to block anything (indeed
if it was, there would be nothing hitting the ISA server). Something
seems to be distorting this traffic when it comes from the remote site,
and I don't know what it is.
Any thoughts?
3.ISA outside IP and PIX firewall
Hi
Can anyone help me on this please, I have a severe lack of understanding!!!
To enable Email I have set up a static command in our PIX firewall, that
specifies a global address for the local host.
My problem is that as we have an ISA server, all internal host are reported
as having the IP address as the outside NIC on ISA. I cannot get the Exchange
server's IP address to pass through ISA, and I am not sure I want to.
However now all externally bound traffic has an IP address transaltes as to
be the same as my Excahnge server's public IP
To get around this I would like to allow the IP address of my internall
Exchange achine to pass through ISA, so that my PIX can then NAT it as
required.
Does this make sense, and can someone tell me how to do it?
Thanks
Lewej
4.FTP outward traffic causing "Unidentified IP traffic" error on ISA 2004 server connected to a PIX
We have a problem with outgoing FTP traffic going through our ISA 2004
server from one of our remote sites. It works absolutely fine from our
main office, but when the traffic originates from our regional office
(we connect to their Pix router via a VPN), it fails every time. The
error from her workstation is "Windows cannot access this folder. Make
sure you type the file name correctly, and that you have permission to
access the folder. Details: the operation timed out". The user has a
Windows XP PC but Windows firewall is switched off. There is a rule our
firewall to allow access from all our subnets (including those from our
regional office), so this should be applicable to all no matter what
their location, however as a test I created a new rule specifically for
the regional office subnet, which failed. I also started logging on the
ISA server, while the user tried this operation again, and the message
stated that the protocol was 'unidentified IP traffic' and the action
was 'closed connection' (the source network was confired as 'internal
however').
The guy who looks after the PIX is away at the moment, but I was
informed by others that it is not configured to block anything (indeed
if it was, there would be nothing hitting the ISA server). Something
seems to be distorting this traffic when it comes from the remote site,
and I don't know what it is.
Any thoughts?