I have installed Sourceoffsite classic ver 4.0 on my server ,Isa server is between Client and server so client not connect to server.
I have read the http://support.sourcegear.com/viewtopic.php?t=258 in Knowledge Base (SourceOffSite) but i could not configure to accept the CONNECT method , how i could configure by CONNECTS method?
OR which proxy server application could be installed on my server compatible to SOS?
thanx
how work client to Sourceofsite server on Isa server(proxy)?
Moderator: SourceGear
The following information was provided by one of the SOS users on our SOS technical mailing list regarding configuring MS ISA on Windows 2000 to give access to port 8080:
It depends which side of the firewall the SOS server will be. For these
purposes, "Client" means the SOS client is behind the firewall, and "Server" means the SOS server is behind the firewall.
First, you need to define the protocols that SOS uses:
In ISA Management, go to Policy Elements / Protocol Definitions
Go Actions... New... Definition
Enter a name for the protocol, e.g. "SOS Client"
Set the following:
For secure client, do the same but with Port Number = 8081
Then for the server side: Create a new definition. e.g. "SOS Server"
Set the following:
Repeat with port 8081 for secure connections.
To allow client access:
Go to "Access Policy / Protocol Rules"
Action... New... Rule
Give it a name, e.g. "allow SOS client"
Rule action: ALLOW
Apply rule to: SOS CLient" (or whatever you named the protocol
definition)
Set scheduling and client-set options according to your needs.
For the server case (server behind the firewall)
Go to "Publishing / Server Publishing Rules"
Action... New... Rules
Enter a name, e.g. "Publish SOS Server"
Enter the IP address of the internal server.
Enter the IP address on the ISA server (or choose "browse" and select the IP address.)
Select the SOS Server protocol defined earlier.
Set "Client Type" as appropriate.
Done... within a couple of minutes, the ISA services will update.
I hope this information is of help.
It depends which side of the firewall the SOS server will be. For these
purposes, "Client" means the SOS client is behind the firewall, and "Server" means the SOS server is behind the firewall.
First, you need to define the protocols that SOS uses:
In ISA Management, go to Policy Elements / Protocol Definitions
Go Actions... New... Definition
Enter a name for the protocol, e.g. "SOS Client"
Set the following:
Secondary Connections: NONEPort Number : 8080
Protocol: TCP
Direction: Outbound
For secure client, do the same but with Port Number = 8081
Then for the server side: Create a new definition. e.g. "SOS Server"
Set the following:
Secondary connections: NONEPort Number : 8080
Protocol : TCP
Direction: Inbound
Repeat with port 8081 for secure connections.
To allow client access:
Go to "Access Policy / Protocol Rules"
Action... New... Rule
Give it a name, e.g. "allow SOS client"
Rule action: ALLOW
Apply rule to: SOS CLient" (or whatever you named the protocol
definition)
Set scheduling and client-set options according to your needs.
For the server case (server behind the firewall)
Go to "Publishing / Server Publishing Rules"
Action... New... Rules
Enter a name, e.g. "Publish SOS Server"
Enter the IP address of the internal server.
Enter the IP address on the ISA server (or choose "browse" and select the IP address.)
Select the SOS Server protocol defined earlier.
Set "Client Type" as appropriate.
Done... within a couple of minutes, the ISA services will update.
I hope this information is of help.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager