You are on page 1of 72

sybrix69 Hi Guys,

New Member
I need some help with ISA 2004 + Publishing OWA. I
have a follow all the document from ISAServer.org and
other articles on the web. Here is the scenario
Posts: 5
Joined:
28.Mar.2008 Network diagram:
Status: offline
[ DMZ]
Internet <---> CISCO PIX <---> NIC-2<---->
ISA2004<---->NIC1<--->LAN
10.32.4.1 10.32.6.50
10.32.4.10
10.32.6.1

Network Interface setup:

NIC 1 - LAN : 10.32.4.10, sub: 255.255.255.0, DNS:


10.32.4.9
Append parent suffixes of the primary DNS suffix
register this connection address in DNS
Enable Netbios over TCP/IP
Client for Microsoft networks, and files and printer
sharing for MS network

NIC 2 - WAN: 10.32.6.50, sub: 255.255.255.0,


GW:10.32.6.1
Disable: Client for Microsoft networks, and files and
printer sharing for MS network
Append parent suffixes of the primary DNS suffix
Disable: Enable Netbios over TCP/IP

Adapter and Binding: 1. LAN --- 2. WAN --- 3.Remote


access connections
Template: Backend network template

Publishing Mail server (template)


From: Anywhere
To: OWA.****.com.au, foward the orginal host header
instead of the actual one
Request appear to come from the ISA Server computer
Listener: OWA SSL Listener; network: External
(10.32.6.50), Enable SSL: 443, certificate:
OWA.****.com.au, Authentication: OW Form-Based,
Domain Name athentication: ****.local
Users: All Users
Bridging: Web server; Redirect request to SSL port: 443
Public Name: OWA.****.com.au

In IIS on Exchange 2003 server, I have follow the M$


doco to change from Integrate authentication to basic
authentication under Exchange/exchweb and annoymous
authentication for /pub.

We purchase a SSL certificate, not using the Windows


Certificate

Currently the only Firewall Policy is OWA WEB


ACCESS and Default rule by the (system policy)

What been tested:

Inside of the LAN network, we able to use


https://****/exchange, a SSL message display "saying
not safe and etc..." hit continues and able to login to
OWA

Add a host file on a PC system which is on the same


segment on the DMZ where the NIC2 (10.32.6.50) of
ISA2004 connected. Host file contain 10.32.6.50 map to
owa.****.com.au. Using Internet explorer with no
proxy server. Was able ping and connected to
https://owa.****.com.au; enter user name and password,
and was directed to the inbox.

Problem here is that I was not able to select any folder in


OWA eg:- inbox, outbox and etc... no contents email
showing

Look at the ISA monitoring log, the follow error


message been captured:-
--------------------------------------------------------------------
---------------
Failed Connection Attempt EPISA01 11/04/2008
12:16:08 PM Log type: Web Proxy (Reverse) Status:
10060 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. Rule: OWA WEB
ACCESS Source: External ( 10.32.6.40:0) Destination:
(owa.****.com.au 10.32.4.11:443) Request: GET
https://owa.****.com.au:443/exchange/ Filter
information: Req ID: 07208dc7 Protocol: https User:
anonymous
Client agent: Mozilla/4.0 (compatible; MSIE 6.0;
Windows NT 5.2; SV1; .NET CLR 1.1.4322)Object
source: Internet Processing time: 21219Cache info:
0x0 MIME
type---------------------------------------------------------------
--------------------
Failed Connection Attempt EPISA01 13/04/2008
8:46:14 AM Log type: Web Proxy (Reverse) Status:
12210 An Internet Server API (ISAPI) filter has finished
handling the request. Contact your system administrator.
Rule: Source: ( 10.32.6.40:0) Destination:
( 10.32.6.50:443) Request: GET
http://owa.****.com.au/CookieAuth.dll?GetLogon?url=
%2Fexchange&reason=0 Filter information: Req ID:
07208ed4 Protocol: https User: anonymous
Client agent: Mozilla/4.0 (compatible; MSIE 6.0;
Windows NT 5.2; SV1; .NET CLR 1.1.4322)Object
source: Processing time: 203Cache info: 0x0 MIME
type:
--------------------------------------------------------------------
---------------

Could anyone see any problem with the setup or have I


miss any steps? Please help or have any suggestion it's
would be great !!!!

Error ID: 10060 - 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.

This error means that Remote Execute could not establish connection to the remote
machine.

It is possible that the remote machine is not running and/or connected to the network.

This error could also be caused by mistyping the remote computer name or address
First verify that the remote machine name/address is indeed valid/correct
(You can try to ping it by choosing “Ping Client” from the Client/Command menu).

If the remote machine name/address is incorrect please change it by editing the client
settings and retry to connect.

Principio del formulario


/w EPDw UJNzE1M

Final del formulario


SQL Server Developer Center
Search SQL

Close
Sign in
United States (English)
Australia (English)Brasil (Português)Česká republika (Čeština)Danmark (Dansk)Deutschland (Deutsch)España
(Español)France (Français)Indonesia (Bahasa)Italia (Italiano)România (Română)Türkiye (Türkçe)Россия (Русский)

대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本


‫)ישראל )עברית(المملكة العربية السعودية )العربية‬ไทย (ไทย)

(日本語)香港特別行政區 (中文)

HomeLibraryLearnDownloadsTroubleshootingCommunityForums
SQL Server Developer Center > SQL Server Forums > SQL Service Broker > Connection
attempt failed with error: 10060
Ask a question
Principio del formulario
Search SQL
Search Forums:
• Search SQL Service Broker Forum
• Search All SQL Server Forums
• Search All MSDN Forums
Forum sqlservicebroker Forum sqlservicebroker

Final del formulario

Connection attempt failed with error: 10060


• Monday, October 20, 2008 7:12 AM dr938

Sign In to Vote

I used the example "Completing a Conversation Between Instances" from SQL Server 2008 Books
Online, but when I try to send a message, it does not go through, and in
sys.transmission_queue.transmission_status I see the above error.

I tried this between two different computers, and also between a


desktop and a VPC running on it, I tried various ports, but nothing helps.
On the profiler I see no activity on the target side.

Thanks for any help.

○ Reply
○ Quote

Answers

• Monday, October 20, 2008 4:01 PM Pawel MarciniakModerator

Sign In to Vote

This is a socket timeout error. Make sure that the target machine listens on the specified TCP
port (e.g. Sql Server TCP Provider is enabled) and there are no firewalls on the way blocking
broker connections. Since this is not a broker-specific issue, so it may be easier to just use telnet
for troubleshooting. Open a shell on the initiator machine and try to execute the following
command.

Code Snippet
telnet.exe target-machine target-broker-port

Once telnet connection is successfull, broker should work as well.

○ Reply
○ Quote

• Tuesday, October 21, 2008 7:06 PM Pawel MarciniakModerator

0
Sign In to Vote
rdoronr wrote:

On the initiator machine: all the services log on as 'NT


AUTHORITY\NETWORK SERVICE'
On the target machine: all the services log on as 'NT
AUTHORITY\NETWORK SERVICE' except the SQL Server browser which
logs on as 'NT AUTHORITY\LOCAL SERVICE'.

It means that when going over the network, Broker will use machine
credentials. Both machines need to be in the same domain (or in
domains with trusted relationship). Let's say the domain is MyDomain,
and the machine names are InitiatorMachine and TargetMachine. You
need to execute the following statements to make connectivity
between server instances possible (again, right now we're talking
about the transport/network level connectivity only).

On the InitiatorMachine:

Code Snippet
GRANT CONNECT ON ENDPOINT::InstInitiatorEndpoint TO
[MyDomain\TargetMachine$]

and on the target machine:

Code Snippet

GRANT CONNECT ON ENDPOINT::InstTargetEndpoint TO


[MyDomain\InitiatorMachine$]
After these steps it should work fine. If it still does not, please provide
the error in transmission status from sys.transmission_queue, as well
as errors in profiler traces from both servers with all events from
Broker group enabled plus additionally Audit Broker Login and
Audit Broker Conversation from the Security Audit group.

○ Reply
○ Quote

All Replies

• Monday, October 20, 2008 4:01 PM Pawel MarciniakModerator

Sign In to Vote

This is a socket timeout error. Make sure that the target machine listens on the specified TCP
port (e.g. Sql Server TCP Provider is enabled) and there are no firewalls on the way blocking
broker connections. Since this is not a broker-specific issue, so it may be easier to just use telnet
for troubleshooting. Open a shell on the initiator machine and try to execute the following
command.

Code Snippet
telnet.exe target-machine target-broker-port

Once telnet connection is successfull, broker should work as well.

○ Reply
○ Quote

• Monday, October 20, 2008 6:19 PM dr938

0
Sign In to Vote

Thanks for the advice.

There was indeed a port mismatch.

Now I advanced to a new set of errors:

On initiator side the errors are:


Connection handshake failed. An OS call failed: (80090303)
0x80090303(failed to retrieve text for this error. Reason: 15105). State
66.
This message could not be delivered because the security context
could not be retrieved.

On target side:
An error occurred while receiving data: 10054

Any ideas?

○ Reply
○ Quote

• Monday, October 20, 2008 6:45 PM Pawel MarciniakModerator

Sign In to Vote
Looks like transport authentication problem. Please provide the
commands you used to create broker endpoints, commands used to
grant connect permissions on the endpoints, and service accounts that
both your Sql Server instances run as.
○ Reply
○ Quote

• Monday, October 20, 2008 7:36 PM dr938

Sign In to Vote

On initiator side:

Code Snippet

USE master;
GO

CREATE ENDPOINT InstInitiatorEndpoint


STATE = STARTED
AS TCP ( LISTENER_PORT = 4022 )
FOR SERVICE_BROKER (AUTHENTICATION = WINDOWS [KERBEROS] );
GO

EXEC sp_grantlogin [MyDomain\MyUser]


GO

CREATE DATABASE InstInitiatorDB;


GO

USE InstInitiatorDB;
GO

-- enable SSB on database


ALTER DATABASE InstInitiatorDB
SET ENABLE_BROKER
WITH ROLLBACK IMMEDIATE
GO
ALTER DATABASE InstInitiatorDB SET TRUSTWORTHY ON
GO

CREATE MASTER KEY


ENCRYPTION BY PASSWORD = N'MyPassword1234';
GO
GO
CREATE USER InitiatorUser WITHOUT LOGIN;
GO

CREATE CERTIFICATE InstInitiatorCertificate


AUTHORIZATION InitiatorUser
WITH SUBJECT = N'Initiator Certificate',
EXPIRY_DATE = N'12/31/2010';

BACKUP CERTIFICATE InstInitiatorCertificate


TO FILE =
N'C:\public\InstInitiatorCertificate.cer';
GO

CREATE USER TargetUser WITHOUT LOGIN;

CREATE CERTIFICATE InstTargetCertificate


AUTHORIZATION TargetUser
FROM FILE =
N'C:\storedcerts\InstTargetCertificate.cer'
GO

CREATE MESSAGE TYPE [RequestMessage]


VALIDATION = WELL_FORMED_XML;
CREATE MESSAGE TYPE [ReplyMessage]
VALIDATION = WELL_FORMED_XML;
GO

CREATE CONTRACT [SimpleContract]


([RequestMessage]
SENT BY INITIATOR,
[ReplyMessage]
SENT BY TARGET
);
GO

CREATE QUEUE InstInitiatorQueue;

CREATE SERVICE InitiatorService


AUTHORIZATION InitiatorUser
ON QUEUE InstInitiatorQueue;
GO

-- Make this user the owner of the initiator service.


ALTER AUTHORIZATION ON SERVICE::InitiatorService TO InitiatorUser
GO

-- Grant send on the service to public.


GRANT SEND ON SERVICE::InitiatorService TO public ;
GO

-- Grant RECEIVE permissions on the queue for the service.


-- This allows the local user to begin conversations from
-- services that use the queue.
GRANT RECEIVE ON InstInitiatorQueue TO public;
GO

DECLARE @Cmd NVARCHAR(4000);


SET @Cmd = N'USE InstInitiatorDB;
CREATE ROUTE InstTargetRoute
WITH SERVICE_NAME =
N''TargetService'',
ADDRESS = N''TCP://project2:4022'';';
EXEC (@Cmd);
GO

DECLARE @Cmd NVARCHAR(4000);


SET @Cmd = N'USE msdb
CREATE ROUTE InstInitiatorRoute
WITH SERVICE_NAME =
N''InitiatorService'',
ADDRESS = N''LOCAL''';
EXEC (@Cmd);
GO

CREATE REMOTE SERVICE BINDING TargetBinding


TO SERVICE 'TargetService'
WITH USER = TargetUser,
ANONYMOUS = ON ;
GO

on the target machine:

Code Snippet

USE master;
GO

CREATE ENDPOINT InstTargetEndpoint


STATE = STARTED
AS TCP ( LISTENER_PORT = 4022 )
FOR SERVICE_BROKER (AUTHENTICATION = WINDOWS [KERBEROS]);
GO

EXEC sp_grantlogin [MyDomainL\MyUser]


GO

CREATE DATABASE InstTargetDB;


GO

ALTER DATABASE InstTargetDB SET TRUSTWORTHY ON


GO
USE InstTargetDB;
GO

CREATE MASTER KEY


ENCRYPTION BY PASSWORD = N'MyPassword1234';
GO

CREATE USER TargetUser WITHOUT LOGIN;


GO

CREATE CERTIFICATE InstTargetCertificate


AUTHORIZATION TargetUser
WITH SUBJECT = 'Target Certificate',
EXPIRY_DATE = N'12/31/2010';

BACKUP CERTIFICATE InstTargetCertificate


TO FILE =
N'C:\windows\temp\InstTargetCertificate.cer';
GO

CREATE MESSAGE TYPE [RequestMessage]


VALIDATION = WELL_FORMED_XML;
CREATE MESSAGE TYPE [ReplyMessage]
VALIDATION = WELL_FORMED_XML;
GO

CREATE CONTRACT SimpleContract


(RequestMessage
SENT BY INITIATOR,
ReplyMessage
SENT BY TARGET
);
GO

CREATE QUEUE InstTargetQueue;

CREATE SERVICE TargetService


AUTHORIZATION TargetUser
ON QUEUE InstTargetQueue
(SimpleContract);
GO

-- Grant receive on the target queue to the local user.


GRANT RECEIVE ON InstTargetQueue TO public;
GO

CREATE USER InitiatorUser WITHOUT LOGIN;


GO

CREATE CERTIFICATE InstInitiatorCertificate


AUTHORIZATION InitiatorUser
FROM FILE =
N'C:\Users\MyUser\Documents\certs\InstInitiatorCertificate.cer';
GO

DECLARE @Cmd NVARCHAR(4000);


SET @Cmd = N'USE InstTargetDB;
CREATE ROUTE InstInitiatorRoute
WITH SERVICE_NAME =
N''InitiatorService'',
ADDRESS = N''TCP://project1:4022'';';
EXEC (@Cmd);
GO

DECLARE @Cmd NVARCHAR(4000);


SET @Cmd = N'USE msdb
CREATE ROUTE InstTargetRoute
WITH SERVICE_NAME =
N''TargetService'',
ADDRESS = N''LOCAL''';
EXEC (@Cmd);
GO

-- Grant send on the service to public.


GRANT SEND ON SERVICE::TargetService TO public ;
GO
CREATE REMOTE SERVICE BINDING InitiatorBinding
TO SERVICE N'InitiatorService'
WITH USER = InitiatorUser;
GO

On both machines the databases are owned by the same user


(displayed above as MyDomain\MyUser).

Thanks

○ Reply
○ Quote

• Monday, October 20, 2008 9:13 PM Pawel MarciniakModerator

Sign In to Vote

You are forcing Sql Server to use Kerberos to authenticate each other.
For that to work, you would need to manually set SPNs for broker
ports. I doubt you're doing it, so instead I would suggest to use
(AUTHENTICATION = WINDOWS) endpoint option, so that it may fall
back to NTLM in case Kerberos authentication is impossible.

The second thing is that I don't see granting connect permission on the
endpoints you created. Connect permission is necessary for one Sql
Server instance to connect to the other. Don't confuse this with dialog
security (for which you're using certificates). This is something
completelly different, happening on the server level rather than
database level.

For example, when your initiator Sql Server instance runs as


MyDomain\MyUser, you need to execute the following statement on
your target instance:

Code Snippet
GRANT CONNECT ON ENDPOINT::InstTargetEndpoint TO
[MyDomain\MyUser]

...and vice-versa.

If your initiator Sql Server instance runs as machine account (e.g. NT


Authority\Network Service), you need to execute the following
statement on your target instance:

Code Snippet
GRANT CONNECT ON ENDPOINT::InstTargetEndpoint TO
[MyDomain\InitiatorHost$]

...and vice-versa.

I hope you get the idea.

○ Reply
○ Quote

• Tuesday, October 21, 2008 12:02 AM dr938

Sign In to Vote

Thank you, Pawel, for your willingness to help. I really appreciate it.

This is the current status:

Pawel Marciniak wrote:

You are forcing Sql Server to use Kerberos to authenticate each other. For
that to work, you would need to manually set SPNs for broker ports. I
doubt you're doing it, so instead I would suggest to use (AUTHENTICATION
= WINDOWS) endpoint option, so that it may fall back to NTLM in case
Kerberos authentication is impossible.

OK. I did that.

Pawel Marciniak wrote:

The second thing is that I don't see granting connect permission on the
endpoints you created. Connect permission is necessary for one Sql
Server instance to connect to the other. Don't confuse this with dialog
security (for which you're using certificates). This is something
completelly different, happening on the server level rather than database
level.

For example, when your initiator Sql Server instance runs as


MyDomain\MyUser, you need to execute the following statement on your
target instance:

Code Snippet
GRANT CONNECT ON ENDPOINT::InstTargetEndpoint TO
[MyDomain\MyUser]
I tried that too, but I got error message saying:

Cannot grant, deny, or revoke permissions to sa, dbo, entity owner,


information_schema, sys, or yourself.

So I tried (based on information I saw somewhere else):

Code Snippet
GRANT CONNECT ON ENDPOINT::InstTargetEndpoint TO [MyDomain\MyUser$]

(added the $) and this completed successfully, but only after I also did

Code Snippet
CREATE LOGIN [MyDomain\MyUser$] FROM WINDOWS

Anyhow - I still get error messages.

I get the same errors on the target like before, and on the initiator I get now in the
profiler:

Connection handshake failed. The login MyDomain\PROJECT2$' does not have


CONNECT permission on the endpoint. State 84.

This message could not be delivered because the security context could not be
retrieved.

where project2 is the name of the target machine

and in the sys.transmission_queue table I get:


Dialog security is unavailable for this conversation because there is no security certificate bound to the database
principal (Id: 5). Either create a certificate for the principal, or specify ENCRYPTION = OFF when beginning the
conversation.

but as you can see above - I do have a certificate

○ Reply
○ Quote

• Tuesday, October 21, 2008 5:38 PM Pawel MarciniakModerator

Sign In to Vote

OK, I think you've gone too far. Let's back up a little. Please let me

know the service accounts of both your instances. You can find them
by running Sql Server Configuration Manager on both machines and
checking the "Log On As" column. Once you know the service
accounts, that will determine what permissions need to be granted on
your endpoint.

Please note that I didn't review the steps you used for certificate
setup, so I'm not saying it's correct. However I've seen that you
deviated from the published tutorial (e.g. by adding [KERBEROS] to the
endpoint creation options). What I would recommend is to follow the
tutorial closely, and only after it starts working adjust the setup to your
needs. That way you will now which change to the default setup
caused problems (i.e. adding [KERBEROS]).

Btw. the dollar sign after an account name means that this is a
machine account rather than user account, so there is really no point
in trying to add '$' after MyDomain\MyUser. It won't make it work.
Good luck!

○ Reply
○ Quote

• Tuesday, October 21, 2008 6:43 PM dr938

Sign In to Vote

Thank you, Pawel.

On the initiator machine: all the services log on as 'NT


AUTHORITY\NETWORK SERVICE'
On the target machine: all the services log on as 'NT
AUTHORITY\NETWORK SERVICE' except the SQL Server browser which
logs on as 'NT AUTHORITY\LOCAL SERVICE'.

The deviations that I introduced were the results of problems to


operate the original example, which prompted me to look all over the
web for solutions (that I tried, in vain), including the KERBEROS thing.

○ Reply
○ Quote

• Tuesday, October 21, 2008 7:06 PM Pawel MarciniakModerator


0

Sign In to Vote
rdoronr wrote:

On the initiator machine: all the services log on as 'NT


AUTHORITY\NETWORK SERVICE'
On the target machine: all the services log on as 'NT
AUTHORITY\NETWORK SERVICE' except the SQL Server browser which
logs on as 'NT AUTHORITY\LOCAL SERVICE'.

It means that when going over the network, Broker will use machine
credentials. Both machines need to be in the same domain (or in
domains with trusted relationship). Let's say the domain is MyDomain,
and the machine names are InitiatorMachine and TargetMachine. You
need to execute the following statements to make connectivity
between server instances possible (again, right now we're talking
about the transport/network level connectivity only).

On the InitiatorMachine:

Code Snippet
GRANT CONNECT ON ENDPOINT::InstInitiatorEndpoint TO
[MyDomain\TargetMachine$]

and on the target machine:

Code Snippet

GRANT CONNECT ON ENDPOINT::InstTargetEndpoint TO


[MyDomain\InitiatorMachine$]
After these steps it should work fine. If it still does not, please provide
the error in transmission status from sys.transmission_queue, as well
as errors in profiler traces from both servers with all events from
Broker group enabled plus additionally Audit Broker Login and
Audit Broker Conversation from the Security Audit group.

○ Reply
○ Quote

• Tuesday, October 21, 2008 8:59 PM dr938

Sign In to Vote

Pawel,

Thank you very much!!

At last the communications works!

These two commands in your last post made the difference.

They are missing from the tutorial example, and initially, when the
tutorial had not worked for me - I tried to add all sorts of "solutions"
proposed for similar situations on the web, some of which probably
only made things worse.
What I did now was to clean up everything, then run the tutorial again
from scratch, but adding the above commands to the respective sides.

There is still one oddity, though: while the profiler does not show
anything on the target side, the profiler on the initiator side still
displays messages:

Broker:Connection An error occurred while receiving data: '64(failed


to retrieve text for this error. Reason: 15105)'.

Broker:Message Undeliverable This message could not be delivered


because the security context could not be retrieved.

even though in initiator sys.transmission_queue there are no rows at


all.

Are these some remnants from before that require some sort of
additional cleanup?

Thanks again.

○ Reply
○ Quote

• Tuesday, October 21, 2008 9:30 PM Pawel MarciniakModerator

0
Sign In to Vote
rdoronr wrote:

There is still one oddity, though: while the profiler does not show anything
on the target side, the profiler on the initiator side still displays messages:

Broker:Connection An error occurred while receiving data: '64(failed to


retrieve text for this error. Reason: 15105)'.

Broker:Message Undeliverable This message could not be delivered


because the security context could not be retrieved.

even though in initiator sys.transmission_queue there are no rows at all.

The first event doesn't necessarily mean there's something wrong. It


will appear every time the other side of the connection closes it due to
90 seconds of inactivity.

The second one, however, is a sign of something bad going on. But
this is dialog security issue (as opposed to transport security, which we
have just successfully sorted out), so for the sake of clarity I would
suggest you to open another topic on the forum for the new issue,
because they are completely unrelated. But first make sure that it isn't
something obvious by looking at Audit Broker Conversation profiler
event from the Security Audit group. It should provide more
information on why the security context cannot be retrieved.

○ Reply
○ Quote

• Tuesday, October 21, 2008 10:04 PM dr938

Sign In to Vote
Once I re-started SQL Server Management Studio and the Profiler - all
these messages ceased to appear, and even after exchanging
messages between the sides - there are no more error messages
anywhere.

Thanks

○ Reply
○ Quote

Need Help with Forums? (FAQ)


My Forum Links
• Sign In To Forums
• Forums Home
• Browse Forums Users
Related Topics

= Unanswered = Answered

• TCP Error Code 10060 on client when service is self-hosted on a ...


• Service Broker Application is getting error + Connection attempt ...
• Help with Microsoft SQL Server, Error: 10060
• SQL Server does not allow remote connections. (
• TCP error code 10060
• Connection timeout eating 20 more seconds than it should given ...
• TCP Error Code 10060 when attempting to access WCF Service hosted ...
• WCF doesn't time out after the specified timeout
• TCP error code 10060 after multiple calls to the WCF Service using ...
• WCF problem
Statistics
• Started: 10/20/2008
• Last Reply: 10/21/2008
• Helpful Votes: 0
• Replies: 12
• Views: 7,041
© 2011 Microsoft. All rights reserved.
Terms of Use|Trademarks|Privacy Statement|Contact Us|Manage Your Profile

Principio del formulario

0 0

Project Cool
An ASP.NET Blog

Enviar

posts - 321, comments - 5514, trackbacks - 1002


Switch to Elastic Layout

<< Update to my post on SQL Azure Migration Wizard | Home | IIS Tools - truck load of them at www.iis.net
>>

Resolving the “TCP error code 10060: A connection attempt failed…” while
consuming a web service

Recently, one of the queries I had was on “TCP error code 10060: 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” while
consuming a web service over proxy settings. Setting the UseDefaultWebProxy to true
didn’t help with this error.

I had earlier written a post on explicitly setting the proxy in the configuration file for
Web Services. The scenario here though was, a WCF Service Client trying to consume
the web service.

However, the same work around proved helpful. After setting the proxy explicitly, the
web service could be consumed by the WCF Client.
The proxy setting that you want to add to the config file is as below:-

<system.net>
<defaultProxy>
<proxy
usesystemdefault = "false"
proxyaddress="http://address:port"
bypassonlocal="false"
/>
</defaultProxy>
</system.net>

This would go within the <configuration> </configuration> tags. You can read the
post written earlier at
http://geekswithblogs.net/ranganh/archive/2005/08/29/51474.aspx

Cheers !!!

posted @ Monday, January 04, 2010 5:08 PM

Print
Comments on this entry:

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by keyword elite at 1/12/2010 10:30 PM

Cheers for that.. I'm not hugely confident with that stuff so thatl help

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by футболки онлайн at 2/8/2010 5:26 AM

Давно искал как это делается, буду чаще заходить на Ваш блог.

# Christian Louboutin
Left by liran313315715 at 3/15/2010 1:53 PM
Welcome to Christian Louboutin , the world’s premier luxury brand of authentic boots, shoes and
slippers.
We guarantee you’ll want to get naked in your Christian Louboutin Shoes ! Christian Louboutin
uses only the highest-grade material available.Our Louboutin UK is now available in stylish new
colors and patterns that will add life to your wardrobe.
Our company carry on various Christian,inc Christian Shoes and Louboutin.

# Nobody can ignore the existence of


Left by liarn at 3/15/2010 1:59 PM

<p>I like the side of the article, and very like your blog, to write well and hope to continue your
efforts, we can see more of your articles.Christian Louboutin shoes. Recommend you to take a
look at it, is now being discounted, Christian Louboutin Fall-Winter Collection in hot! </p>

# Christian louboutin shoes


Left by summer at 3/29/2010 5:09 PM

Thanks of your infomation,i have read it is very helpful for me.


One of my friend told me some information about
Christian louboutin,then i search them on the Internet,they are so
beautiful.
cheap christian louboutin shoes

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by louboutinvips at 4/1/2010 6:41 PM
If you want to buy a pair of beautiful shoes
http://www.christianlouboutinvips.com

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by louboutinshopz at 4/2/2010 5:32 PM

welcome to our online shop ,we will give you the best .

http://www.christianlouboutinolshop.com

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by louboutinvips at 4/2/2010 5:36 PM

welcome to our shop!


you will own the best!
http://www.christianlouboutinvips.com
http://www.christianlouboutinvips.com

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by bolum izle at 4/3/2010 5:53 AM

Thanks of your infomation,i have read it is very helpful for me.


One of my friend told me some information about
Christian louboutin,then i search them on the Internet,they are so
beautiful.
# re: Resolving the “TCP error code 10060: A connection
attempt failed…” while consuming a web service
Left by ysl boots at 4/6/2010 1:26 AM

It was a very nice idea! Just wanna say thank you for the information you have shared.

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by louboutin shoes at 4/7/2010 6:01 PM

After setting the proxy explicitly, the web service could be consumed by the WCF Client.
GHD straighteners
cheap christian louboutin shoes

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by sexy shoes at 4/7/2010 6:53 PM

Cheap ghd hair straighteners on sale,free shipping!


cheap christian louboutin boots,louboutin boots on sale

http://www.onsale-ghd.com
http://www.mychristianlouboutinshoes.com

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by saylor at 4/9/2010 3:15 PM
That's interesting. christian louboutin shoes

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by SharePoint Courses at 4/10/2010 6:37 AM

Its always good to learn tips like you share for blog posting. As I just started posting comments
for blog and facing problem of lots of rejections. I think your suggestion would be helpful for me. I
will let you know if its work for me too. Thank you for sharing this beautiful articles. keep going,
best of luck

# Select - travel to 5 star London hotels.Try adventure


travel to Africa
Left by Baron at 4/11/2010 7:39 AM

Choose - tour to 4 star Florence hotels, 4 star hotel in Rome, 4 star hotels in Venice.Luxury
cruises.Get air line ticket voucher now.

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by cl boots at 4/11/2010 2:45 PM

Shoes are not only made with fashion in mind; they are also made to be comfortable.
cheapsexyshoes

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by puma at 4/13/2010 7:56 PM

I found this post while searching google. Quite surprising too, since google usually displays
relatively old results but this one is very recent! Anyway, very informative, especially since this is
not something many people tend to write something good about. any words i like puma shoes
Take care…

# re: mbt shoes


Left by mbtshoes123 at 4/17/2010 12:31 AM

Hello everyone.
In our online shop, you can purchase different designer mbt shoes, and we offer the commodities
are high in quality and reasonable at price now.
These are our mbt shoes on sale.
Shop's homepage www.mbtshoeshop-online.com
[URL=http://www.mbtshoeshop-online.com]mbt shoes[/URL]
<a href=\"http://www.mbtshoeshop-online.com\">mbt men

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by Herniated Neck Disk at 4/19/2010 7:09 AM

I got a good definition for TCP error code 10060: 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. Cheers

# re: cheap Christian louboutin shoes


Left by cheap Christian louboutin shoes at 4/19/2010 8:11 PM
HOLLE!
In our online shop, you can purchase different designer mbt shoes, and we offer the commodities
are high in quality and reasonable at price now.

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by Bankruptcy Services at 4/21/2010 12:53 AM

Just do certain operations, your issue will be resolved.


1. Please run Dynamsoft SCM Anywhere Standalone Service Configurator as administrator, and
then click menu Service | Start Service.
2. Please make sure that all routers & firewalls between SCM Anywhere Client & Server, and any
firewall software on the machine hosting SCM Anywhere Server (i.e. Windows Firewall, etc..) are
properly configured to allow the necessary traffic to pass through.

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by UK ED Hardy at 4/21/2010 11:26 PM

a great source of informative knowledge which is very beneficial for everybody

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by supra shoe at 4/28/2010 8:43 PM

s o what can i do

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by Koiran Vaatteet at 5/2/2010 4:00 AM
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.

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by Moncler Jackets at 5/2/2010 8:16 PM

Welcome to Moncler Jackets online shop.The 2010 latest and most fashionable Jackets,save up to
60% off. 7 days delivery to worldwide with free shipping.
Our aim is to provide customers high-quality products and excellent after-sales service.

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by True Religion jeans at 5/2/2010 8:17 PM

We launched the 2010 latest and most fashionable True Religion jeans on our shop, you are
welcome to patronize.Here are many discounts for you.
Our aim is to provide high-quality products and excellent after-sales service.

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by air purifiers at 5/3/2010 8:02 AM

I Googled this error & found your site. It has been very helpful, not only for this error, but other
issues.

# discount watches
Left by snzdheh@yahoo.com at 5/6/2010 2:08 PM
The new high can browse your article

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by jungle force boots at 5/6/2010 6:48 PM

Another reason that I would regard joining a political party to be such a valuable thing is that
dramatically positive and liberating experience.

# re: R: A connection attempt failed…” while consuming a


web service
Left by britax marathon at 5/9/2010 7:21 PM

You write some very informative blogs. I always check back here often to see if you have
updated.

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by Freestyle Medela at 5/12/2010 6:44 AM

It's a great pleasure for me to say that you have been more than impressive, just keep this
impression like this for years to come.
Chris Harris
Freestyle Medela

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by louboutin at 5/14/2010 12:00 AM

<p>Thank you for your sharing. Supposed to attack these head-on and you will find a deep
sense of gratification thatwill fuel your happiness. Maybe you are also interested in Christian
Louboutin shoes. I'm just hearing the curiosity behind it.

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by Confidence Course High Wycombe at 5/16/2010 8:44 AM

Thanks for solving this - I'm never quite sure what to do with these kind of errors. Cheers, Dan

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by wholeslae at 5/28/2010 7:41 PM

Thank you for your psot!


p90x

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by Auto Insurance at 5/30/2010 10:58 AM

I've surfed the net more than three hours today

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by meksika biberi zayiflama hapi at 5/31/2010 11:41 PM
good nice

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by prada handbags at 6/5/2010 1:33 AM

what can i do

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by Lemonade Diet Pill at 6/5/2010 9:56 PM

Thanks for the advice

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by Replica Relojes Corum at 6/6/2010 9:45 PM

nice!!
i like it!

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by Tattoo Designs at 6/6/2010 11:06 PM
cheers for the advice

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by christianlouboutin9 at 6/10/2010 2:49 AM

http://finechristianlouboutin.com/
our finechristianlouboutin.com sell well-designed christian shoes, whichever style of shoes you"re
looking for, classical, fashionable,lovely or the latest design, you can find your favorite christian
louboutin shoes here. you may find it amazing in their looks if it"s the first time for you to see
them. we promise, you"ll love them.

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by Male cams at 7/8/2010 10:28 PM

Thanks for solving this - I'm never quite sure what to do with these kind of errors. James

# re: louis handbags


Left by lv-sales at 7/12/2010 8:14 PM

just to leave my name and i fu le you

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by ciphone c5 at 7/23/2010 3:51 PM

thanks for you share!


# Thanks
Left by fm transmitter at 8/14/2010 12:52 PM

I liked it very much. PLease keep sharing this type of blogs in the future also.

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by Hostess at 9/11/2010 2:56 PM

Resolving the error is an enigma for me still. Even after reading this post I can not do anything
with it. The errors are consuming my time a lot.

# air purifiers
Left by m tomas at 10/2/2010 6:47 AM

Before you buy any smaller hepa filter air purifier you need to read up on its filter. How often
does it have to be changed and how much does each one cost?

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by arnab dutta at 11/12/2010 4:14 PM

i am using proxifier to bypass the proxy settings of my college. i am getting this message when i
try to connect. what should i do?

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by Anthony at 12/15/2010 10:38 PM
This worked perfectly for me. Thanks for saving me a great deal of time by hunting down the
solutions.

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by rooby at 1/6/2011 9:21 PM

Architectural Interiors is a company of consultants specialising in the design and fit-out of


commercial office interiors. We are passionately committed to creating cost effective workplace
environments whilst incorporating your individual needs. Our background and knowledge in
office design is exceptional making us one of the leading creative builders in the business.
office design build
office interior design

# re: Resolving the “TCP error code 10060: A connection


attempt failed…” while consuming a web service
Left by artrepro at 2/12/2011 8:43 AM

I am just new to your blog and just spent about 1 hour and 30 minutes lurking and reading. I
think I will frequent your blog from now on after going through some of your posts. I will
definitely learn a lot from them.Wedding dress
Bridal Gowns
Your comment:

Title:

re: Resolving t

Please enter a title


Name:
Please enter your name
Email:

(will not be displayed)


Email is not required, but it must be valid if specified.
Website:

Url is not required, but it must be valid if specified.


Comment:

Please enter a comment

Remember Me?

Enter the code shown abovePlease

DqPYtRsoD7I7Gd
enter the correct word
Comment Reset

Live Comment Preview:

« February »
Su Mo Tu We Th
Fri Sat
n n e d u
30 31 1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 1 2 3 4 5
6 7 8 9 10 11 12

ASP.NET
Promote Your Page Too

About

• Contact

• Login

Twitter

ranganh VTD WebMatrix session by Harish rocks #vtd about 2 days ago

ranganh Nokia and Microsoft :)http://www.m...1/02-11partnership.mspx about 2 days ago

ranganh URL for attending VTD www.virtualtechdays.com #vtd about 4 days ago

ranganh Virtual TechDays 2011 happening right now #vtd about 4 days ago

ranganh HTML5 and Visual Studio 2010 http://tinyu...s2010 about 6 days ago

ranganh Microosft adds H.264 support to Google Chrome http://tinyu...zr @doctypehtml5 about 10 days ago

ranganh Microsoft adds H.264 support to Google Chrome http://tinyu...7zr #doctypehtml5 about 10 days ago

ranganh @roopesh_reddy roopesh, webcamps last city would be Kochi. Will let you know when the next round of webcamps happen about
11 days ago

ranganh Mobile device detection and redirection for ASP.NET applications http://51deg....com/ about 12 days ago

ranganh @tweetsmilu .NET 4.0 came along with Visual Studio 2010. Are you looking for something specific? about 17 days ago

Archives

• February, 2011 (1)

• January, 2011 (1)

• October, 2010 (2)


• September, 2010 (2)

• July, 2010 (4)

• May, 2010 (5)

• April, 2010 (1)

• March, 2010 (2)

• February, 2010 (2)

• January, 2010 (2)

• December, 2009 (7)

• November, 2009 (1)

• October, 2009 (2)

• September, 2009 (7)

• August, 2009 (5)

• July, 2009 (6)

• June, 2009 (4)

• May, 2009 (11)

• April, 2009 (4)

• March, 2009 (6)

• February, 2009 (4)

• January, 2009 (5)

• December, 2008 (5)

• November, 2008 (4)

• October, 2008 (9)

• September, 2008 (5)

• August, 2008 (4)

• July, 2008 (2)


• June, 2008 (2)

• April, 2008 (3)

• March, 2008 (1)

• February, 2008 (8)

• January, 2008 (8)

• December, 2007 (5)

• November, 2007 (5)

• October, 2007 (2)

• August, 2007 (3)

• July, 2007 (5)

• June, 2007 (4)

• May, 2007 (14)

• April, 2007 (3)

• March, 2007 (3)

• February, 2007 (8)

• January, 2007 (8)

• November, 2006 (9)

• October, 2006 (5)

• September, 2006 (1)

• August, 2006 (1)

• June, 2006 (2)

• May, 2006 (2)

• April, 2006 (2)

• March, 2006 (2)

• February, 2006 (4)


• January, 2006 (5)

• December, 2005 (7)

• November, 2005 (4)

• October, 2005 (3)

• September, 2005 (9)

• August, 2005 (4)

• July, 2005 (6)

• June, 2005 (7)

• May, 2005 (11)

• April, 2005 (42)

Post Categories

• ASP.NET

• Windows Vista

• Visual Studio

• Events

• Silverlight

• Windows Live

• Windows XP

• Microsoft Office

• Video

• Windows Azure

• Internet Explorer

• Web Development

• Microsoft Expression

• TechEd India 2009


• Security

• Windows 7

• SQL Server

• Entity Framework

• WebMatrix

• Razor

• Personal

• Microsoft

• Internet Explorer

• Windows Mobile

• HTML5

Blogs I read

• Lakshmi

• Pandurang Nayak

• Scott Guthrie

• Somasegar

• Vinod Kumar

Syndication:

RSS ATOM
© Harish Ranganathan
Theme by PiyoDesign. Valid XHTML & CSS.

When you are programming in php within windows os and you received HTTP ERROR: Couldn't
open socket connection to server. Error (10060): 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.

The Reason and solution for socket error 10060 and solution is
given bellow
A.Windows firewall blocking connection:

The most probable reason for socket


connection not working in windows os is because of
the firewall of windows os does not allow the
socket network communication. IN Windows 7 and
Vista you can solved the socket error using Opening
port for communicate and allow all access to this
port.
Steps to open port in windows 7:

Go to Control Panel-->Security and Settings-->Windows Firewall


Advanced Settings-->Inbound Rules-->New rule
Select port-->Click Next-->Select as TCP and Add Your Server Port

For Example For PHP it is 8080 or 80 port number and for mail service
it is port 25 .
Do the same procedure for the outbound Rules.
B.Your DNS Name is not resolved properly.
If Your DNS name is not resolved properlly then this error might
occure.In case of local host If Your localhost is not Resolved properlly
then you can try 127.0.0.1 this might work for you. example:
http://127.0.0.1:80/webservice/nusoap/server/server.php?wsdl

C. Your Script might not properlly response because of Timeout of socket connection.
Newsgrupos.com > Forum > Principio del formulario
Newsgroup Nombre de Usuario N o m b re d e
microsoft.public.es.* 1 Foro > ¿Recordarme?
Newsgroup Contraseña In ic iaSer s ió n
microsoft.public.es.isaserver
8ee95f55ef0b745 login
tunel entre empresas
- no llego a webserver
Final del formulario

Preguntas Lista de Calendari Temas de


Registrarse Buscar
Frecuentes Foreros o Hoy

Buscar en los Foros


Principio del formulario
process 1 1 1 8ee95f55ef0b745

Ir

Mostrar Temas Mostrar Posts


Final del formulario

Búsqueda Avanzada

Ir a la Página...
Principio del formulario

Final del formulario

Página 1 de
12>
2

LinkBack Herramientas Desplegado

#1
04-09-2008, 16:42:55

Alejo [CAP] Mensajes: n/a


tunel entre empresas - no llego
a webserver
tenemos que ingresar a unos
server web de la otra red
conectada por un
tunel. usamos PROXY para
navegar y puse exclusiones del
rango ip que tiene
la otra red. igualmente sigo sin
poder conectarme.

este mensaje aparece todo el


tiempo.

Log type: Web Proxy (Forward)


Status: 10060 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.

Closed Connection Server1


9/4/2008 12:38:45 PM
Log type: Firewall service
Status: A connection was
gracefully closed in an orderly
shutdown process
with a three-way FIN-initiated
handshake.
Rule:
Source: Local Host
( 190.2.xxx.yyy:15631)
Destination: VPN - RED2--RED1
( 10.aaa.0.ccc:80)
Protocol: HTTP

lo que observo tambien es que


intenta salir por la IP publica el
requerimiento y no por tunel
VPN

espero se haya entendido.

gracias.
alejo.

Today
This advertising will not be shown
in this way to registered members.
Advertising Register your free account today
Google Adsense and become a member on
Newsgrupos.com
Sponsored Links

#2
04-09-2008, 17:13:47
El niño santo de Emaus Mensajes: n/a
Re: tunel entre empresas - no llego a webserver
Hola Alejo. ¿El túnel es de tipo IPSec?

Saludos

// Raúl

--
Check my blog at http://edgesecurity.blogspot.com

---------------------------------------------------------------------------------
"Alejo [CAP]" <alko26***nospam.hotmail.com> wrote in message
news:ulXaK1qDJHA.3636***TK2MSFTNGP02.phx.gbl...
> tenemos que ingresar a unos server web de la otra red conectada por un
> tunel. usamos PROXY para navegar y puse exclusiones del rango ip que tiene
> la otra red. igualmente sigo sin poder conectarme.
>
> este mensaje aparece todo el tiempo.
>
> Log type: Web Proxy (Forward)
> Status: 10060 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.
>
> Closed Connection Server1 9/4/2008 12:38:45 PM
> Log type: Firewall service
> Status: A connection was gracefully closed in an orderly shutdown process
> with a three-way FIN-initiated handshake.
> Rule:
> Source: Local Host ( 190.2.xxx.yyy:15631)
> Destination: VPN - RED2--RED1 ( 10.aaa.0.ccc:80)
> Protocol: HTTP
>
> lo que observo tambien es que intenta salir por la IP publica el
> requerimiento y no por tunel VPN
>
> espero se haya entendido.
>
> gracias.
>
> alejo.

#3
04-09-2008, 17:13:47
El niño santo de Emaus Mensajes: n/a
Re: tunel entre empresas - no llego a webserver
Hola Alejo. ¿El túnel es de tipo IPSec?

Saludos

// Raúl

--
Check my blog at http://edgesecurity.blogspot.com

---------------------------------------------------------------------------------
"Alejo [CAP]" <alko26***nospam.hotmail.com> wrote in message
news:ulXaK1qDJHA.3636***TK2MSFTNGP02.phx.gbl...
> tenemos que ingresar a unos server web de la otra red conectada por un
> tunel. usamos PROXY para navegar y puse exclusiones del rango ip que tiene
> la otra red. igualmente sigo sin poder conectarme.
>
> este mensaje aparece todo el tiempo.
>
> Log type: Web Proxy (Forward)
> Status: 10060 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.
>
> Closed Connection Server1 9/4/2008 12:38:45 PM
> Log type: Firewall service
> Status: A connection was gracefully closed in an orderly shutdown process
> with a three-way FIN-initiated handshake.
> Rule:
> Source: Local Host ( 190.2.xxx.yyy:15631)
> Destination: VPN - RED2--RED1 ( 10.aaa.0.ccc:80)
> Protocol: HTTP
>
> lo que observo tambien es que intenta salir por la IP publica el
> requerimiento y no por tunel VPN
>
> espero se haya entendido.
>
> gracias.
>
> alejo.

#4
04-09-2008, 22:47:34
Alejo [CAP] Mensajes: n/a
Re: tunel entre empresas - no llego a webserver
si, de un lado isa 2004 sp3/win2003sp2 y del otro Cisco ASA

gracias

"El niño santo de Emaus" <rmoros***kabel.es> wrote in message


news:#N3SWGrDJHA.504***TK2MSFTNGP02.phx.gbl...
> Hola Alejo. ¿El túnel es de tipo IPSec?
>
> Saludos
>
> // Raúl
>
> --
> Check my blog at http://edgesecurity.blogspot.com
>
> ---------------------------------------------------------------------------------
> "Alejo [CAP]" <alko26***nospam.hotmail.com> wrote in message
> news:ulXaK1qDJHA.3636***TK2MSFTNGP02.phx.gbl...
>> tenemos que ingresar a unos server web de la otra red conectada por un
>> tunel. usamos PROXY para navegar y puse exclusiones del rango ip que
>> tiene la otra red. igualmente sigo sin poder conectarme.
>>
>> este mensaje aparece todo el tiempo.
>>
>> Log type: Web Proxy (Forward)
>> Status: 10060 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.
>>
>> Closed Connection Server1 9/4/2008 12:38:45 PM
>> Log type: Firewall service
>> Status: A connection was gracefully closed in an orderly shutdown process
>> with a three-way FIN-initiated handshake.
>> Rule:
>> Source: Local Host ( 190.2.xxx.yyy:15631)
>> Destination: VPN - RED2--RED1 ( 10.aaa.0.ccc:80)
>> Protocol: HTTP
>>
>> lo que observo tambien es que intenta salir por la IP publica el
>> requerimiento y no por tunel VPN
>>
>> espero se haya entendido.
>>
>> gracias.
>>
>> alejo.
>
>

#5
04-09-2008, 22:47:34
Alejo [CAP] Mensajes: n/a
Re: tunel entre empresas - no llego a webserver
si, de un lado isa 2004 sp3/win2003sp2 y del otro Cisco ASA

gracias

"El niño santo de Emaus" <rmoros***kabel.es> wrote in message


news:#N3SWGrDJHA.504***TK2MSFTNGP02.phx.gbl...
> Hola Alejo. ¿El túnel es de tipo IPSec?
>
> Saludos
>
> // Raúl
>
> --
> Check my blog at http://edgesecurity.blogspot.com
>
> ---------------------------------------------------------------------------------
> "Alejo [CAP]" <alko26***nospam.hotmail.com> wrote in message
> news:ulXaK1qDJHA.3636***TK2MSFTNGP02.phx.gbl...
>> tenemos que ingresar a unos server web de la otra red conectada por un
>> tunel. usamos PROXY para navegar y puse exclusiones del rango ip que
>> tiene la otra red. igualmente sigo sin poder conectarme.
>>
>> este mensaje aparece todo el tiempo.
>>
>> Log type: Web Proxy (Forward)
>> Status: 10060 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.
>>
>> Closed Connection Server1 9/4/2008 12:38:45 PM
>> Log type: Firewall service
>> Status: A connection was gracefully closed in an orderly shutdown process
>> with a three-way FIN-initiated handshake.
>> Rule:
>> Source: Local Host ( 190.2.xxx.yyy:15631)
>> Destination: VPN - RED2--RED1 ( 10.aaa.0.ccc:80)
>> Protocol: HTTP
>>
>> lo que observo tambien es que intenta salir por la IP publica el
>> requerimiento y no por tunel VPN
>>
>> espero se haya entendido.
>>
>> gracias.
>>
>> alejo.
>
>
#6
05-09-2008, 07:56:26
El niño santo de Emaus Mensajes: n/a
Re: tunel entre empresas - no llego a webserver
Supongo que has definido subredes para la red interna y la remota y has
creado una relación entre redes de Route ¿no?. Si no lo has hecho, te
recomiendo hacerlo. A continuación define un protocolo con el nombre que te
guste que sea de tipo Outbound TCP puerto 80 (sí, lo mismo que HTTP.
Importante, no le asocies ningún filtro). Haz una regla arriba del todo
permitiendo este protocolo entre la red interna y la remota. Justo debajo
haz otra regla denegando HTTP (el estándar) entre la red interna y la
remota.

Espero que funcione. Si es así te explico porqué creo que te está pasando

Saludos

// Raúl

--
Check my blog at http://edgesecurity.blogspot.com

---------------------------------------------------------------------------------
"Alejo [CAP]" <alko26***nospam.hotmail.com> wrote in message
news:Osxr6AuDJHA.4104***TK2MSFTNGP05.phx.gbl...
> si, de un lado isa 2004 sp3/win2003sp2 y del otro Cisco ASA
>
> gracias
>
>
> "El niño santo de Emaus" <rmoros***kabel.es> wrote in message
> news:#N3SWGrDJHA.504***TK2MSFTNGP02.phx.gbl...
>> Hola Alejo. ¿El túnel es de tipo IPSec?
>>
>> Saludos
>>
>> // Raúl
>>
>> --
>> Check my blog at http://edgesecurity.blogspot.com
>>
>> ---------------------------------------------------------------------------------
>> "Alejo [CAP]" <alko26***nospam.hotmail.com> wrote in message
>> news:ulXaK1qDJHA.3636***TK2MSFTNGP02.phx.gbl...
>>> tenemos que ingresar a unos server web de la otra red conectada por un
>>> tunel. usamos PROXY para navegar y puse exclusiones del rango ip que
>>> tiene la otra red. igualmente sigo sin poder conectarme.
>>>
>>> este mensaje aparece todo el tiempo.
>>>
>>> Log type: Web Proxy (Forward)
>>> Status: 10060 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.
>>>
>>> Closed Connection Server1 9/4/2008 12:38:45 PM
>>> Log type: Firewall service
>>> Status: A connection was gracefully closed in an orderly shutdown
>>> process with a three-way FIN-initiated handshake.
>>> Rule:
>>> Source: Local Host ( 190.2.xxx.yyy:15631)
>>> Destination: VPN - RED2--RED1 ( 10.aaa.0.ccc:80)
>>> Protocol: HTTP
>>>
>>> lo que observo tambien es que intenta salir por la IP publica el
>>> requerimiento y no por tunel VPN
>>>
>>> espero se haya entendido.
>>>
>>> gracias.
>>>
>>> alejo.
>>
>>

#7
05-09-2008, 07:56:26
El niño santo de Emaus Mensajes: n/a
Re: tunel entre empresas - no llego a webserver
Supongo que has definido subredes para la red interna y la remota y has
creado una relación entre redes de Route ¿no?. Si no lo has hecho, te
recomiendo hacerlo. A continuación define un protocolo con el nombre que te
guste que sea de tipo Outbound TCP puerto 80 (sí, lo mismo que HTTP.
Importante, no le asocies ningún filtro). Haz una regla arriba del todo
permitiendo este protocolo entre la red interna y la remota. Justo debajo
haz otra regla denegando HTTP (el estándar) entre la red interna y la
remota.

Espero que funcione. Si es así te explico porqué creo que te está pasando

Saludos

// Raúl

--
Check my blog at http://edgesecurity.blogspot.com

---------------------------------------------------------------------------------
"Alejo [CAP]" <alko26***nospam.hotmail.com> wrote in message
news:Osxr6AuDJHA.4104***TK2MSFTNGP05.phx.gbl...
> si, de un lado isa 2004 sp3/win2003sp2 y del otro Cisco ASA
>
> gracias
>
>
> "El niño santo de Emaus" <rmoros***kabel.es> wrote in message
> news:#N3SWGrDJHA.504***TK2MSFTNGP02.phx.gbl...
>> Hola Alejo. ¿El túnel es de tipo IPSec?
>>
>> Saludos
>>
>> // Raúl
>>
>> --
>> Check my blog at http://edgesecurity.blogspot.com
>>
>> ---------------------------------------------------------------------------------
>> "Alejo [CAP]" <alko26***nospam.hotmail.com> wrote in message
>> news:ulXaK1qDJHA.3636***TK2MSFTNGP02.phx.gbl...
>>> tenemos que ingresar a unos server web de la otra red conectada por un
>>> tunel. usamos PROXY para navegar y puse exclusiones del rango ip que
>>> tiene la otra red. igualmente sigo sin poder conectarme.
>>>
>>> este mensaje aparece todo el tiempo.
>>>
>>> Log type: Web Proxy (Forward)
>>> Status: 10060 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.
>>>
>>> Closed Connection Server1 9/4/2008 12:38:45 PM
>>> Log type: Firewall service
>>> Status: A connection was gracefully closed in an orderly shutdown
>>> process with a three-way FIN-initiated handshake.
>>> Rule:
>>> Source: Local Host ( 190.2.xxx.yyy:15631)
>>> Destination: VPN - RED2--RED1 ( 10.aaa.0.ccc:80)
>>> Protocol: HTTP
>>>
>>> lo que observo tambien es que intenta salir por la IP publica el
>>> requerimiento y no por tunel VPN
>>>
>>> espero se haya entendido.
>>>
>>> gracias.
>>>
>>> alejo.
>>
>>

#8
05-09-2008, 07:59:26
El niño santo de Emaus Mensajes: n/a
Re: tunel entre empresas - no llego a webserver
Por cierto, veo que ya conseguiste establecer el túnel. ¿Cuál era el truco?
¿Tenía que ver con el NAT-T como sospechábamos?

// Raúl

--
Check my blog at http://edgesecurity.blogspot.com

---------------------------------------------------------------------------------
"Alejo [CAP]" <alko26***nospam.hotmail.com> wrote in message
news:Osxr6AuDJHA.4104***TK2MSFTNGP05.phx.gbl...
> si, de un lado isa 2004 sp3/win2003sp2 y del otro Cisco ASA
>
> gracias
>
>
> "El niño santo de Emaus" <rmoros***kabel.es> wrote in message
> news:#N3SWGrDJHA.504***TK2MSFTNGP02.phx.gbl...
>> Hola Alejo. ¿El túnel es de tipo IPSec?
>>
>> Saludos
>>
>> // Raúl
>>
>> --
>> Check my blog at http://edgesecurity.blogspot.com
>>
>> ---------------------------------------------------------------------------------
>> "Alejo [CAP]" <alko26***nospam.hotmail.com> wrote in message
>> news:ulXaK1qDJHA.3636***TK2MSFTNGP02.phx.gbl...
>>> tenemos que ingresar a unos server web de la otra red conectada por un
>>> tunel. usamos PROXY para navegar y puse exclusiones del rango ip que
>>> tiene la otra red. igualmente sigo sin poder conectarme.
>>>
>>> este mensaje aparece todo el tiempo.
>>>
>>> Log type: Web Proxy (Forward)
>>> Status: 10060 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.
>>>
>>> Closed Connection Server1 9/4/2008 12:38:45 PM
>>> Log type: Firewall service
>>> Status: A connection was gracefully closed in an orderly shutdown
>>> process with a three-way FIN-initiated handshake.
>>> Rule:
>>> Source: Local Host ( 190.2.xxx.yyy:15631)
>>> Destination: VPN - RED2--RED1 ( 10.aaa.0.ccc:80)
>>> Protocol: HTTP
>>>
>>> lo que observo tambien es que intenta salir por la IP publica el
>>> requerimiento y no por tunel VPN
>>>
>>> espero se haya entendido.
>>>
>>> gracias.
>>>
>>> alejo.
>>
>>

#9
05-09-2008, 07:59:26
El niño santo de Emaus Mensajes: n/a
Re: tunel entre empresas - no llego a webserver
Por cierto, veo que ya conseguiste establecer el túnel. ¿Cuál era el truco?
¿Tenía que ver con el NAT-T como sospechábamos?

// Raúl

--
Check my blog at http://edgesecurity.blogspot.com
---------------------------------------------------------------------------------
"Alejo [CAP]" <alko26***nospam.hotmail.com> wrote in message
news:Osxr6AuDJHA.4104***TK2MSFTNGP05.phx.gbl...
> si, de un lado isa 2004 sp3/win2003sp2 y del otro Cisco ASA
>
> gracias
>
>
> "El niño santo de Emaus" <rmoros***kabel.es> wrote in message
> news:#N3SWGrDJHA.504***TK2MSFTNGP02.phx.gbl...
>> Hola Alejo. ¿El túnel es de tipo IPSec?
>>
>> Saludos
>>
>> // Raúl
>>
>> --
>> Check my blog at http://edgesecurity.blogspot.com
>>
>> ---------------------------------------------------------------------------------
>> "Alejo [CAP]" <alko26***nospam.hotmail.com> wrote in message
>> news:ulXaK1qDJHA.3636***TK2MSFTNGP02.phx.gbl...
>>> tenemos que ingresar a unos server web de la otra red conectada por un
>>> tunel. usamos PROXY para navegar y puse exclusiones del rango ip que
>>> tiene la otra red. igualmente sigo sin poder conectarme.
>>>
>>> este mensaje aparece todo el tiempo.
>>>
>>> Log type: Web Proxy (Forward)
>>> Status: 10060 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.
>>>
>>> Closed Connection Server1 9/4/2008 12:38:45 PM
>>> Log type: Firewall service
>>> Status: A connection was gracefully closed in an orderly shutdown
>>> process with a three-way FIN-initiated handshake.
>>> Rule:
>>> Source: Local Host ( 190.2.xxx.yyy:15631)
>>> Destination: VPN - RED2--RED1 ( 10.aaa.0.ccc:80)
>>> Protocol: HTTP
>>>
>>> lo que observo tambien es que intenta salir por la IP publica el
>>> requerimiento y no por tunel VPN
>>>
>>> espero se haya entendido.
>>>
>>> gracias.
>>>
>>> alejo.
>>
>>

#10
08-09-2008, 01:46:33
Alejo [CAP] Mensajes: n/a
Re: tunel entre empresas - no llego a webserver
no comprendo lo del filtro.

me podes enviar como seria la regla ?

gracias.
alejo

"El niño santo de Emaus" <rmoros***kabel.es> wrote in message


news:#dCVvzyDJHA.4696***TK2MSFTNGP04.phx.gbl...
> Supongo que has definido subredes para la red interna y la remota y has
> creado una relación entre redes de Route ¿no?. Si no lo has hecho, te
> recomiendo hacerlo. A continuación define un protocolo con el nombre que
> te guste que sea de tipo Outbound TCP puerto 80 (sí, lo mismo que HTTP.
> Importante, no le asocies ningún filtro). Haz una regla arriba del todo
> permitiendo este protocolo entre la red interna y la remota. Justo debajo
> haz otra regla denegando HTTP (el estándar) entre la red interna y la
> remota.
>
> Espero que funcione. Si es así te explico porqué creo que te está pasando
>
> Saludos
>
> // Raúl
>
> --
> Check my blog at http://edgesecurity.blogspot.com
>
> ---------------------------------------------------------------------------------
> "Alejo [CAP]" <alko26***nospam.hotmail.com> wrote in message
> news:Osxr6AuDJHA.4104***TK2MSFTNGP05.phx.gbl...
>> si, de un lado isa 2004 sp3/win2003sp2 y del otro Cisco ASA
>>
>> gracias
>>
>>
>> "El niño santo de Emaus" <rmoros***kabel.es> wrote in message
>> news:#N3SWGrDJHA.504***TK2MSFTNGP02.phx.gbl...
>>> Hola Alejo. ¿El túnel es de tipo IPSec?
>>>
>>> Saludos
>>>
>>> // Raúl
>>>
>>> --
>>> Check my blog at http://edgesecurity.blogspot.com
>>>
>>> ---------------------------------------------------------------------------------
>>> "Alejo [CAP]" <alko26***nospam.hotmail.com> wrote in message
>>> news:ulXaK1qDJHA.3636***TK2MSFTNGP02.phx.gbl...
>>>> tenemos que ingresar a unos server web de la otra red conectada por un
>>>> tunel. usamos PROXY para navegar y puse exclusiones del rango ip que
>>>> tiene la otra red. igualmente sigo sin poder conectarme.
>>>>
>>>> este mensaje aparece todo el tiempo.
>>>>
>>>> Log type: Web Proxy (Forward)
>>>> Status: 10060 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.
>>>>
>>>> Closed Connection Server1 9/4/2008 12:38:45 PM
>>>> Log type: Firewall service
>>>> Status: A connection was gracefully closed in an orderly shutdown
>>>> process with a three-way FIN-initiated handshake.
>>>> Rule:
>>>> Source: Local Host ( 190.2.xxx.yyy:15631)
>>>> Destination: VPN - RED2--RED1 ( 10.aaa.0.ccc:80)
>>>> Protocol: HTTP
>>>>
>>>> lo que observo tambien es que intenta salir por la IP publica el
>>>> requerimiento y no por tunel VPN
>>>>
>>>> espero se haya entendido.
>>>>
>>>> gracias.
>>>>
>>>> alejo.
>>>
>>>
>
>

Página 1 de
12>
2

« Tema Anterior | Próximo Tema »


Principio del formulario
Herramientas
Mostrar Versión Imprimible

Enviar por Correo

Final del formulario


Desplegado

Mode Lineal

Cambiar a Modo

Hibrido
Cambiar a Modo Hilado

Temas Similares
Respuest Último
Tema Autor Foro
as mensaje

tunel entre 27-10-


Alejo Newsgroup
checkpoint con isa 0 2008
[CAP] microsoft.public.es.isaserver
server 2004 13:13:19

05-08-
tunel entre cisco Alejo Newsgroup
3 2008
asa5510 con isa 2004 [CAP] microsoft.public.es.isaserver
09:15:41

Newsgrupos Italiano - Newsgrupos Français - Newsgrupos English - Newsgrupos German -


Newsgrupos Niuz

La franja horaria es GMT. Ahora son las 00:32:05.

Principio del formulario

-- Español 3.6.5 - Newsgrupos Home Page - Archivo - Top

Derechos de Autor ©2000 - 2011, Newsgrupos.com


Powered by vBulletin Copyright © 2010 vBulletin Solutions, Inc.
Final del formulario
LinkBack

LinkBack URL

About LinkBacks
Bookmark & Share

Digg this Thread!

Add Thread to del.icio.us

Bookmark in Technorati

Furl this Thread!

LinkBacks Enabled by vBSEO 3.1.0 © 2007, Crawlability, Inc.

Principio del formulario


/w EPDw UJNzE1M

Final del formulario


Recursos para Profesionales de TI
Buscar Tech

Cierre
Sign in
España (Español)
Australia (English)Brasil (Português)Česká republika (Čeština)Danmark (Dansk)Deutschland (Deutsch)France
(Français)Indonesia (Bahasa)Italia (Italiano)Magyarország (Magyar)România (Română)Singapore (English)Türkiye

(Türkçe)United States (English)Россия (Русский) ‫)ישראל )עברית(المملكة العربية السعودية )العربية‬ไทย (ไทย) 대한민국 (한
국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語)香港特別行政區 (中文)
Resources for IT Professionals

InicioBibliotecaAprendizajeDescargaSoporteComunidadForos
Recursos para Profesionales de TI > Página principal de foros > Foros de Seguridad > Protección y
acceso (Edge Security / ISA Server) > LAN no accede a servidor WEB interno
Formular una pregunta
Principio del formulario
Buscar en el f
Búsqueda de foros:
• Buscar en el foro de Protección y acceso (Edge Security / ISA Server)
• Buscar en todos los foros de Seguridad
• Buscar en todos los foros de Microsoft TechNet
Forum forefrontedgees Forum forefrontedgees
Final del formulario

LAN no accede a servidor WEB interno


• martes, 27 de abril de 2010 14:59 omar.moreno

Inicie sesión para votar

Mi LAN no puede acceder a un servidor web interno, este servidor esta bajo un Active Directory, este
es el escesario:

Isa 2006 bajo un Active Directory, dominio bajo WinServer 2003 configurados los DNS de ISP como
reenviadores, Servidor WEB en red interna bajo Active Directory.

El detalle esque si este Servidor WEB lo saco del dominio la red interna si accede a la pagina web de
este servidor.

Ayuda por favor.

○ Responder

○ Citar

Respuestas

• viernes, 07 de mayo de 2010 21:12 Jimcesse

Inicie sesión para votar

Me da mucho gusto Omar... No olvides cerrar el hilo, marcando la respuesta...

Saludos,

Jimcesse

○ Marcado como respuestaomar.moreno sábado, 08 de mayo de 2010 16:55



○ Responder

○ Citar
Todas las respuestas

• miércoles, 05 de mayo de 2010 18:56 GregoJ

Inicie sesión para votar

Hola Omar,

El problema parece de DNS, ¿Has probado que la resolución en los clientes es correcta?

Un saludo

GregoJ

"Saber que se sabe lo que se sabe y que no se sabe lo que no se sabe; he aquí el verdadero saber."
Confucio

○ Responder

○ Citar

• miércoles, 05 de mayo de 2010 22:35 omar.moreno

Inicie sesión para votar

Gracias pro contestar GregoJ, el problema se genera cuando el servidow WEB interno lo agrego al
Dominio ya que si lo dejo en un grupo de trabajo no tengo ningun problema,

En cuanto la resolucion de nombres DNS, te comento que en el servidor ISA cuento con una regla
que permite HTTP, HTTPS y DNS de la red interna a red interna y al servidor WEB interno.

alguna otra sugerencia gracias

○ Responder

○ Citar
• miércoles, 05 de mayo de 2010 23:05 Jimcesse

Inicie sesión para votar


Como ingresas a la pagina web (IP, Nombre del Server o dominio) ???

Jimcesse

○ Responder

○ Citar

• miércoles, 05 de mayo de 2010 23:16 omar.moreno

Inicie sesión para votar

Ingreso con IP

PD. La regla en isaserver 2006 la he publicado para que la red interna acceda ya se por IP o por
nombre de servidor WEB

○ Responder

○ Citar

• jueves, 06 de mayo de 2010 7:50 GregoJ

Inicie sesión para votar

Omar ¿Que error muestra la pagina del explorador?

Un saludo

GregoJ

"Saber que se sabe lo que se sabe y que no se sabe lo que no se sabe; he aquí el verdadero saber."
Confucio
○ Responder

○ Citar

• viernes, 07 de mayo de 2010 2:08 omar.moreno

Inicie sesión para votar

Este es el log que me da el monitor de Isa:

Failed Connection Attempt FRWLSVR 5/6/2010 7:04:02 PM


Log type: Web Proxy (Forward)
Status: 10060 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.
Rule: LocalHost
Source: Local Host (192.168.1.3)
Destination: Internal (sisaimhanil.hanil.com 192.168.1.226:80)
Request: GET http://192.168.1.226/
Filter information: Req ID: 0a90207b; Compression: client=No, server=No, compress rate=0%
decompress rate=0%
Protocol: http
User: anonymous
Additional information
Client agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; SV1; GTB6.4; .NET CLR
1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30)
Object source: Internet (Source is the Internet. Object was added to the cache.)
Cache info: 0x0
Processing time: 62938 ms
MIME type:

○ Responder

○ Citar

• viernes, 07 de mayo de 2010 7:26 Jimcesse

Inicie sesión para votar


Omar,

Si agregas el servidor al domino y tratas de accesar al WEB localmente (osea desde el localhost) la
puedes ver ???

Por otro lado antes del ISA tienes algun otro Firewall (aunque sea el de Windows o anti-virus) ???

Que sistema operativo tiene el servidor donde tienes el WEB instalado ???

Aplicas politicas de grupo para los miembros de tu dominio ???

Saludos,

Jimcesse

○ Responder

○ Citar

• viernes, 07 de mayo de 2010 14:35 omar.moreno

Inicie sesión para votar


Problema resuelto, era el firewall de windows el que me bloqueaba la aplicacion del servidor web,
uso apache como servidor, muchas gracias.
○ Responder

○ Citar

• viernes, 07 de mayo de 2010 21:12 Jimcesse

Inicie sesión para votar

Me da mucho gusto Omar... No olvides cerrar el hilo, marcando la respuesta...

Saludos,

Jimcesse

○ Marcado como respuestaomar.moreno sábado, 08 de mayo de 2010 16:55



○ Responder

○ Citar

¿Necesita ayuda con los foros? (P+F)

Mis vínculos de foros


• Iniciar sesión en los foros
• Página principal de foros
• Examinar usuarios de los foros

Temas relacionados

= Sin respuesta = Respondida

• No veo mi WEB publicada desde mi LAn


• Acceso OWA desde Internet
• Configuración ISA + DNS
• Configurar servidor DNS para que resuelva servicios publicados en ...
• error de autenticación al acceder al owa desde el exterior

Estadísticas
• Comenzado: 27/04/2010
• Última respuesta: 07/05/2010
• Votos útiles: 0
• Respuestas: 9
• Visualizaciones: 467

© 2011 Microsoft. Reservados todos los derechos.


Administre su perfil|Contacte con nosotros|Boletín|Condiciones de Uso|Marcas Registradas|
Declaración de privacidad
In this case you can inscrese timeout parameter for connecting socket.Final del formulario

You might also like