To do that i use surrogate socket and it work well . I try it with winsock but it doesn't seems to work well . I say to my isa server if you receive a request on my proxy on port 3389 you relay it to my WTS server on port 3389 and it works well > Laurent Chuzel - Architecture Sécurité NT RES\DOS\IRS\INL\INT > lchuzel@xxxxxxxxxxxxxxxxxx > Tél : 01.41.09.27.06 > VENI VIDI VICI > -----Message d'origine----- > De: Aleksander França Honma [SMTP:aleks@xxxxxxxxxxxxxx] > Date: lundi 22 octobre 2001 14:46 > À: [ISAserver.org Discussion List] > Objet: [isalist] TSWeb problem > > http://www.ISAserver.org > > > Hi All, > > I published Terminal Service Web Access according to Tom's > instructions. > My TSWeb Server is on separate machine from ISA. > Accessing TS using Web client form the local network works. When I > access TS using Web client from outside I get Terminal Services Web > Connection page, but after entering server name and clicking on Connect, I > get VBScript: Error connecting to terminal server: server_name. > > Does anybody knows what's happening. > > The inbound Protocol Definition was created and a Packet Filter was also > created for Inbound on 3389. > > A thing that I found to be strange, the IIS/Terminal Server is doing > socket > pooling, so it's listening on 0.0.0.0:3389 instead of the private IP > assigned to it. (is this OK?) > > Another thing, after Sniffering the network for the logon activity (from > the > LAN), it seems that the transport is as follows: > > MY machine TSWEb > any port -> 3389 > > TSWeb My maching > 3389 -> any port > > Now thinking on this, why did I create an INBOUND on the fixed port 3389 > for > ISA LOCAL machine? > > Any clues are more than welcome. > > Aleks > > > ------------------------------------------------------ > You are currently subscribed to this ISAserver.org Discussion List as: > lchuzel@xxxxxxxxxxxxxxxxxx > To unsubscribe send a blank email to $subst('Email.Unsub')