Hi!
I have strange situation after deploing WebService
in client environment. WebService is written in .NET 2.0,
resides on separate site (Win 2003) and is secured by SSL.

And when client applications try to connect using
IP number (https://192.168.100.100:8892/Service.asmx)
I get strange error "System.Net.WebException: The underlying connection
was closed: An unexpected error occurred on a send. --->
System.IO.IOException: The handshake failed due to an unexpected packet
format."
- on most machines, but on 2 machines connecting goes OK.

But when I connect using host name (https://host:8892/Service.asmx)
everything works OK...

Why connecting by IP can cause an error? Where to search for a reason?

Regards

Mrozik

What is the "common name" (cn property) of the certificate? If the cn has
the "host name" then you'd get an error connecting by IP address (the
address youare connecting to does not match the address embedded in the
certificate)

Cheers
Ken


"Mrozik" <mrozik.p [at] interia.pl> wrote in message
news:op.tvpdmiucy3yzc4 [at] n1054.mshome.net...
> Hi!
> I have strange situation after deploing WebService
> in client environment. WebService is written in .NET 2.0,
> resides on separate site (Win 2003) and is secured by SSL.
>
> And when client applications try to connect using
> IP number (https://192.168.100.100:8892/Service.asmx)
> I get strange error "System.Net.WebException: The underlying connection
> was closed: An unexpected error occurred on a send. --->
> System.IO.IOException: The handshake failed due to an unexpected packet
> format."
> - on most machines, but on 2 machines connecting goes OK.
>
> But when I connect using host name (https://host:8892/Service.asmx)
> everything works OK...
>
> Why connecting by IP can cause an error? Where to search for a reason?
>
> Regards
>
> Mrozik

On Mon, 23 Jul 2007 01:51:47 +0200, Ken Schaefer
<kenREMOVE [at] THISadOpenStatic.com> wrote:

> What is the "common name" (cn property) of the certificate? If the cn
> has the "host name" then you'd get an error connecting by IP address
> (the address youare connecting to does not match the address embedded in
> the certificate)

Why application installed on 2 machines can connect by IP?

What should be common name of certificate to enable communicating
by IP - different from host name?

regards

Mrozik


>
> Cheers
> Ken
>
>
> "Mrozik" <mrozik.p [at] interia.pl> wrote in message
> news:op.tvpdmiucy3yzc4 [at] n1054.mshome.net...
>> Hi!
>> I have strange situation after deploing WebService
>> in client environment. WebService is written in .NET 2.0,
>> resides on separate site (Win 2003) and is secured by SSL.
>>
>> And when client applications try to connect using
>> IP number (https://192.168.100.100:8892/Service.asmx)
>> I get strange error "System.Net.WebException: The underlying connection
>> was closed: An unexpected error occurred on a send. --->
>> System.IO.IOException: The handshake failed due to an unexpected packet
>> format."
>> - on most machines, but on 2 machines connecting goes OK.
>>
>> But when I connect using host name (https://host:8892/Service.asmx)
>> everything works OK...
>>
>> Why connecting by IP can cause an error? Where to search for a reason?
>>
>> Regards
>>
>> Mrozik
>



--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/