TS Gateway access is not working Prakashkumaar 12/17/2008 3:33:02 PM Hi My setup is as follows Active Directory Domain Controller on Windows 2003 R2 Terminal Server on Windows 2008 64 Bit Gateway protection on ISA2006 - Windows 2003 R2 I am accessing my Terminal server over TS Gateway via ISA 2006. Everything was working fine for last six months. Suddenly from last night I could connect to my Terminal server via TS gateway. I am able to access terminal server from Internal network. Checked the event logs on TS. There is no error related to TS Gateway. I checked in ISA server and I could find only one event log related to this as follows. Event Type: Error Event Source: Microsoft ISA Server Web Proxy Event Category: None Event ID: 14200 Date: 16/12/2008 Time: 14:09:01 User: N/A Computer: SVR03 Description: ISA Server was unable to establish an SSL connection with svr01.domian.com. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. I used the ISA traffic monitor when I connect through TS Gateway. There was an error as follows Failed Connection Attempt SVR03 17/12/2008 15:27:44 Log type: Web Proxy (Reverse) Status: 64 The specified network name is no longer available. Rule: TS GATEWAY Source: External (111.11.11.1) Destination: (172.16.100.220:443) Request: RPC_IN_DATA https://svr01.domain.com:443/rpc/rpcproxy.dll?localhost:3388 Filter information: Req ID: 09cccc5d; Compression: client=No, server=No, compress rate=0% decompress rate=0% Protocol: https User: anonymous Additional information Client agent: MSRPC Object source: Internet (Source is the Internet. Object was added to the cache.) Cache info: 0x8 (Request includes the AUTHORIZATION header.) Processing time: 578 ms MIME type: I am able ping the Terminal server - svr01.domain.com from ISA. As an alternative solution to access the Terminal server for remote users, I have setup the VPN and asked them to use without TS gateway settings which works fine. I spend many hours to get this TS gateway access issue resolved but nothing worked out. Please advice to get this resolved.

RE: TS Gateway access is not working Prakashkumaar 12/18/2008 6:54:00 AM This issue has been resovled. The problem was on the Terminal server - IIS configuration. We deployed a new application on the default website which modified the home directory of default website. After revert back our application TS web access started working. Thanks Prakash "Prakashkumaar" wrote: [Quoted Text] > Hi > > My setup is as follows > > Active Directory Domain Controller on Windows 2003 R2 > Terminal Server on Windows 2008 64 Bit > Gateway protection on ISA2006 - Windows 2003 R2 > > I am accessing my Terminal server over TS Gateway via ISA 2006. Everything > was working fine for last six months. Suddenly from last night I could > connect to my Terminal server via TS gateway. I am able to access terminal > server from Internal network. Checked the event logs on TS. There is no error > related to TS Gateway. I checked in ISA server and I could find only one > event log related to this as follows. > > Event Type: Error > Event Source: Microsoft ISA Server Web Proxy > Event Category: None > Event ID: 14200 > Date: 16/12/2008 > Time: 14:09:01 > User: N/A > Computer: SVR03 > Description: > ISA Server was unable to establish an SSL connection with svr01.domian.com. > A connection attempt failed because the connected party did not properly > respond after a period of time, or established connection failed because > connected host has failed to respond. > > I used the ISA traffic monitor when I connect through TS Gateway. There was > an error as follows > > Failed Connection Attempt SVR03 17/12/2008 15:27:44 > Log type: Web Proxy (Reverse) > Status: 64 The specified network name is no longer available. > Rule: TS GATEWAY > Source: External (111.11.11.1) > Destination: (172.16.100.220:443) > Request: RPC_IN_DATA > https://svr01.domain.com:443/rpc/rpcproxy.dll?localhost:3388 > Filter information: Req ID: 09cccc5d; Compression: client=No, server=No, > compress rate=0% decompress rate=0% > Protocol: https > User: anonymous > Additional information > Client agent: MSRPC > Object source: Internet (Source is the Internet. Object was added to the > cache.) > Cache info: 0x8 (Request includes the AUTHORIZATION header.) > Processing time: 578 ms > MIME type: > > > > I am able ping the Terminal server - svr01.domain.com from ISA. > > As an alternative solution to access the Terminal server for remote users, I > have setup the VPN and asked them to use without TS gateway settings which > works fine. > > I spend many hours to get this TS gateway access issue resolved but nothing > worked out. > > Please advice to get this resolved. >

RE: TS Gateway access is not working Kaus 12/23/2008 6:29:01 AM Hi Prakash, Since there are no event logs on the TS or the TSG , this could be specifically a name resolution or ISA issue. Can you please try doing the following things : 1. Instead of pinging TSG, try opening the link https://svr01.domain.com:443/rpc through a web browser. This will tell you whether the pinged ip is actually the TSG ip.Flush the dns cache on the ISA to get the latest address from DNS. 2. Check to see whether in the TS Gateway rule on ISA the IP for the svr01.domain.com has not bee hardcoded. There is an option where you can specify the ip of the internal site being published in the ISA rule. 3. Try clearing the ISA cache and see if that works. Thanks, Kaus. "Prakashkumaar" wrote: [Quoted Text] > Hi > > My setup is as follows > > Active Directory Domain Controller on Windows 2003 R2 > Terminal Server on Windows 2008 64 Bit > Gateway protection on ISA2006 - Windows 2003 R2 > > I am accessing my Terminal server over TS Gateway via ISA 2006. Everything > was working fine for last six months. Suddenly from last night I could > connect to my Terminal server via TS gateway. I am able to access terminal > server from Internal network. Checked the event logs on TS. There is no error > related to TS Gateway. I checked in ISA server and I could find only one > event log related to this as follows. > > Event Type: Error > Event Source: Microsoft ISA Server Web Proxy > Event Category: None > Event ID: 14200 > Date: 16/12/2008 > Time: 14:09:01 > User: N/A > Computer: SVR03 > Description: > ISA Server was unable to establish an SSL connection with svr01.domian.com. > A connection attempt failed because the connected party did not properly > respond after a period of time, or established connection failed because > connected host has failed to respond. > > I used the ISA traffic monitor when I connect through TS Gateway. There was > an error as follows > > Failed Connection Attempt SVR03 17/12/2008 15:27:44 > Log type: Web Proxy (Reverse) > Status: 64 The specified network name is no longer available. > Rule: TS GATEWAY > Source: External (111.11.11.1) > Destination: (172.16.100.220:443) > Request: RPC_IN_DATA > https://svr01.domain.com:443/rpc/rpcproxy.dll?localhost:3388 > Filter information: Req ID: 09cccc5d; Compression: client=No, server=No, > compress rate=0% decompress rate=0% > Protocol: https > User: anonymous > Additional information > Client agent: MSRPC > Object source: Internet (Source is the Internet. Object was added to the > cache.) > Cache info: 0x8 (Request includes the AUTHORIZATION header.) > Processing time: 578 ms > MIME type: > > > > I am able ping the Terminal server - svr01.domain.com from ISA. > > As an alternative solution to access the Terminal server for remote users, I > have setup the VPN and asked them to use without TS gateway settings which > works fine. > > I spend many hours to get this TS gateway access issue resolved but nothing > worked out. > > Please advice to get this resolved. >