RE: Routing to VPN access server issue on ISA 2004
- From: <hugh@xxxxxxxxxxxx>
- To: <isalist@xxxxxxxxxxxxx>
- Date: Tue, 21 Sep 2004 13:54:55 +0200
At this rate it is going to be...
-----Original Message-----
From: Greg Mulholland [mailto:greg@xxxxxxxxxxxxxx]
Sent: 21 September 2004 12:28 PM
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: Routing to VPN access server issue on ISA 2004
http://www.ISAserver.org
You say that like it's a bad thing :P
-----Original Message-----
From: hugh@xxxxxxxxxxxx [mailto:hugh@xxxxxxxxxxxx]
Sent: Tuesday, September 21, 2004 6:05 PM
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: Routing to VPN access server issue on ISA 2004
http://www.ISAserver.org
I too am struggling with the same routing issues in ISA 2004, and it is
driving me to drink. Well, more than usual.
Hopefully the experts can shed some light.
Regards,
Hugh
-----Original Message-----
From: A.J. Boudewijn [mailto:isa@xxxxxxxxxxxx]
Sent: 20 September 2004 12:40 PM
To: [ISAserver.org Discussion List]
Subject: [isalist] Routing to VPN access server issue on ISA 2004
http://www.ISAserver.org
Hi,
We are just testing with ISA 2004 server and have an issue with routing.
Working Situation:
A)Windows 2000 + ISA 2000 server. Routing and Remote Access enabled.
RIP.
B)Windows 2003 Remote Access Server. RIP. VPN dialer to 192.168.100.0
network.
Client workstations use the ISA as default gateway. When they want to go
to the 192.168.100.0 network they are routed by the ISA to the Windows
2003 Remote Access Server. They are able to ping to Internet and the
192.168.100.0 network.
New situation:
A)Windows 2003 + ISA 2004 server. Routing and Remote Access enabled.
RIP.
B)Windows 2003 Remote Access Server. RIP. VPN dialer to 192.168.100.0
network.
Client workstations use the ISA 2004 as default gateway. When they want
to go to the 192.168.100.0 network they are not routed by the ISA 2004
to the Windows 2003 Remote Access Server. They are able to ping to
Internet, but no able to ping the 192.168.100.0 network. We can also
ping the Windows
2003 Remote Access Server.
The Routing table on ISA 2004 shows the route to 192.168.100.0 Its
receiving the route from the Windows 2003 (B) We created an access rule
for PING to all remote, local host and internal network.
We still have an action denied in the logging of the ISA 2004 server
when pinging from a client workstation to the 192.168.100.0 network. The
name of the rule is empty , so I guess this is an impliciet/system rule
that cause that we are not able to ping / reach the 192.168.100.0
network.
What can cause this ? Any idea?
Thanks,
Albert Jan Boudewijn
------------------------------------------------------
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:
hugh@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:
greg@xxxxxxxxxxxxxx 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:
hugh@xxxxxxxxxxxx
To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist
Report abuse to listadmin@xxxxxxxxxxxxx
Other related posts:
