Re: ISA 2004 Blocking LAN Traffic

  • From: "Stephen Herrera" <sherrera@xxxxxxxxxx>
  • To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
  • Date: Thu, 16 Sep 2004 09:38:27 -0700

It isn't, that is what is puzzling me. They are all SNAT clients. The 
communication that I am referring to being blocked is BEHIND the ISA 2004 
Server.

Lan --> ISA 2k4 --> DMZ --> ISA 2k --> Internet


Steve

 -----Original Message-----
From:   Jim Harrison [mailto:jim@xxxxxxxxxxxx] 
Sent:   Thursday, September 16, 2004 9:09 AM
To:     [ISAserver.org Discussion List]
Subject:        [isalist] Re: ISA 2004 Blocking LAN Traffic

http://www.ISAserver.org

Why is your ISA between the clients and the DC?
Are your clients using the FW client?

  Jim Harrison
  MCP(NT4, W2K), A+, Network+, PCG
  http://isaserver.org/Jim_Harrison/
  http://isatools.org
  Read the help / books / articles!

----- Original Message ----- 
From: "Stephen Herrera" <sherrera@xxxxxxxxxx>
To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
Sent: Thursday, September 16, 2004 09:01
Subject: [isalist] ISA 2004 Blocking LAN Traffic


http://www.ISAserver.org

I have been testing ISA2004 for a few weeks now to replace my existing ISA 2000 
servers. Everything has been going very well but I 
was testing while no users were on the network.

Yesterday I put the ISA 2004 server in place of my Internal ISA 2000 Server 
(back to back setup) and the network came to a 
screeching halt. I had tested and configured all the basics (http, mail, ftp, 
etc.) while it was just myself and everything was 
fine. When all users were on the network they were working spotty.

I checked the logs and noticed that a lot of internal network talking (DNS, 
NetBios, LDAP, etc) was being blocked between internal 
clients and the domain controllers. Even the domain controllers were being 
blocked from communicating with each other. I have 
checked isaserver.org and MS knowledge base but can't find anything like this 
happening. For a quick fix I tired creating a rule 
that allows all traffic from internal to internal but that didn't seem to work. 
Any idea what I might have configured wrong?

Steve


------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist
ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp
ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
World of Windows Networking: http://www.windowsnetworking.com
Leading Network Software Directory: http://www.serverfiles.com
No.1 Exchange Server Resource Site: http://www.msexchange.org
Windows Security Resource Site: http://www.windowsecurity.com/
Network Security Library: http://www.secinf.net/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as: 
jim@xxxxxxxxxxxx
To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist
Report abuse to listadmin@xxxxxxxxxxxxx


------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist
ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp
ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
World of Windows Networking: http://www.windowsnetworking.com
Leading Network Software Directory: http://www.serverfiles.com
No.1 Exchange Server Resource Site: http://www.msexchange.org
Windows Security Resource Site: http://www.windowsecurity.com/
Network Security Library: http://www.secinf.net/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as: 
sherrera@xxxxxxxxxx
To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist
Report abuse to listadmin@xxxxxxxxxxxxx




Other related posts: