By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,665 Members | 1,586 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,665 IT Pros & Developers. It's quick & easy.

Windows 2000 Server vs. Professional

P: n/a
I have developed a VB.net application that transfers a
SOAP wrapped message to another server securely(using SSL
and sever/client certificates). When I run this app from
a Windows 2000 Professional box everything works as
expected, the secure channel is established and the
message is sent properly. When I use the exact same app
on the Windows 2000 Server(running IIS) box the app does
not work properly. I have used a packet sniffer to try
and see what is going on and it appears the server cannot
establish a secure connection with the remote server.(All
the appropriate certificates are installed on both boxes)
IS there some setting which needs to be changed in Windows
2000 Server in order for this to work??? (I am logged into
the Windows 2000 Server as a client/ it is not running as
a service). I don't understand why this would work under
Windows 2000 Profession and not under Windows 2000
Server. Any help in resolving this issue would be greatly
appreciated. Thanks in advance.
Nov 22 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Sample code might help. Generally when those types of issues arrive. There
is an issue with security permissions. Have you made any changes to your
machine.config?
Are you using impersonation?

Let me know.

Nick
"Dave" <an*******@discussions.microsoft.com> wrote in message
news:04****************************@phx.gbl...
I have developed a VB.net application that transfers a
SOAP wrapped message to another server securely(using SSL
and sever/client certificates). When I run this app from
a Windows 2000 Professional box everything works as
expected, the secure channel is established and the
message is sent properly. When I use the exact same app
on the Windows 2000 Server(running IIS) box the app does
not work properly. I have used a packet sniffer to try
and see what is going on and it appears the server cannot
establish a secure connection with the remote server.(All
the appropriate certificates are installed on both boxes)
IS there some setting which needs to be changed in Windows
2000 Server in order for this to work??? (I am logged into
the Windows 2000 Server as a client/ it is not running as
a service). I don't understand why this would work under
Windows 2000 Profession and not under Windows 2000
Server. Any help in resolving this issue would be greatly
appreciated. Thanks in advance.

Nov 22 '05 #2

P: n/a
We have not made any changes to the Machine.config and we are not using impersonation...It is the standard installation of Windows 2000 Server running IIS with a server certificate installed on the machine. Here is the code I am using to establish the connection...again bear in mind that this exact same code works with Windows 2000 Professional, so I'm kinda leaning to some sort of configuration issue

Dim objRequest As HttpWebReques
Dim objResponse As HttpWebRespons
Dim objWriter As StreamWrite
Dim objReader As StreamReade
Dim objCertificate As X509Certificat

Tr
objCertificate = objCertificate.CreateFromCertFile(CertificatePath

'Initializes HTTP properties for communicatio
If RequestType = MISORequestType.SUBMIT_REQUEST The
objRequest = CType(objRequest.Create("https://" & SUBMIT_URL), HttpWebRequest
ElseIf RequestType = MISORequestType.QUERY_REQUEST The
objRequest = CType(objRequest.Create("https://" & QUERY_URL), HttpWebRequest
End I

'Adds a Client Certificat
objRequest.ClientCertificates.Add(objCertificate

'Set up some configuration for using HTTPWebReques
objRequest.Method = "POST
objRequest.ContentLength = XMLMessage.Lengt
objRequest.ContentType = "Content-Type: text/xml" ' heade

'Sends the HTTP POST command over the strea
MsgBox("About to send the message to MISO"
objWriter = New StreamWriter(objRequest.GetRequestStream()
objWriter.Write(XMLMessage
objWriter.Close(
MsgBox("Message Sent waiting for response"
'Sets Timeout to 60 second
objRequest.Timeout = 6000
'Gets the response back from the HTTP Post Reques
objResponse = CType(objRequest.GetResponse(), HttpWebResponse

ResponseCode = objResponse.StatusCod

'Reads the response back into Text forma
objReader = New StreamReader(objResponse.GetResponseStream(), Encoding.UTF8
ResponseMessage = objReader.ReadToEnd(
objReader.Close(

Catch e As Exceptio
MsgBox(e.Message & " " & e.InnerException.Message
End Tr
Return Tru
----- Nick Harris wrote: ----

Sample code might help. Generally when those types of issues arrive. Ther
is an issue with security permissions. Have you made any changes to you
machine.config
Are you using impersonation

Let me know

Nic
"Dave" <an*******@discussions.microsoft.com> wrote in messag
news:04****************************@phx.gbl..
I have developed a VB.net application that transfers
SOAP wrapped message to another server securely(using SS
and sever/client certificates). When I run this app fro
a Windows 2000 Professional box everything works a
expected, the secure channel is established and th
message is sent properly. When I use the exact same ap
on the Windows 2000 Server(running IIS) box the app doe
not work properly. I have used a packet sniffer to tr
and see what is going on and it appears the server canno
establish a secure connection with the remote server.(Al
the appropriate certificates are installed on both boxes
IS there some setting which needs to be changed in Window
2000 Server in order for this to work??? (I am logged int
the Windows 2000 Server as a client/ it is not running a
a service). I don't understand why this would work unde
Windows 2000 Profession and not under Windows 200
Server. Any help in resolving this issue would be greatl
appreciated. Thanks in advance


Nov 22 '05 #3

P: n/a
Sample code might help. Generally when those types of issues arrive. There
is an issue with security permissions. Have you made any changes to your
machine.config?
Are you using impersonation?

Let me know.

Nick
"Dave" <an*******@discussions.microsoft.com> wrote in message
news:04****************************@phx.gbl...
I have developed a VB.net application that transfers a
SOAP wrapped message to another server securely(using SSL
and sever/client certificates). When I run this app from
a Windows 2000 Professional box everything works as
expected, the secure channel is established and the
message is sent properly. When I use the exact same app
on the Windows 2000 Server(running IIS) box the app does
not work properly. I have used a packet sniffer to try
and see what is going on and it appears the server cannot
establish a secure connection with the remote server.(All
the appropriate certificates are installed on both boxes)
IS there some setting which needs to be changed in Windows
2000 Server in order for this to work??? (I am logged into
the Windows 2000 Server as a client/ it is not running as
a service). I don't understand why this would work under
Windows 2000 Profession and not under Windows 2000
Server. Any help in resolving this issue would be greatly
appreciated. Thanks in advance.

Nov 22 '05 #4

P: n/a
We have not made any changes to the Machine.config and we are not using impersonation...It is the standard installation of Windows 2000 Server running IIS with a server certificate installed on the machine. Here is the code I am using to establish the connection...again bear in mind that this exact same code works with Windows 2000 Professional, so I'm kinda leaning to some sort of configuration issue

Dim objRequest As HttpWebReques
Dim objResponse As HttpWebRespons
Dim objWriter As StreamWrite
Dim objReader As StreamReade
Dim objCertificate As X509Certificat

Tr
objCertificate = objCertificate.CreateFromCertFile(CertificatePath

'Initializes HTTP properties for communicatio
If RequestType = MISORequestType.SUBMIT_REQUEST The
objRequest = CType(objRequest.Create("https://" & SUBMIT_URL), HttpWebRequest
ElseIf RequestType = MISORequestType.QUERY_REQUEST The
objRequest = CType(objRequest.Create("https://" & QUERY_URL), HttpWebRequest
End I

'Adds a Client Certificat
objRequest.ClientCertificates.Add(objCertificate

'Set up some configuration for using HTTPWebReques
objRequest.Method = "POST
objRequest.ContentLength = XMLMessage.Lengt
objRequest.ContentType = "Content-Type: text/xml" ' heade

'Sends the HTTP POST command over the strea
MsgBox("About to send the message to MISO"
objWriter = New StreamWriter(objRequest.GetRequestStream()
objWriter.Write(XMLMessage
objWriter.Close(
MsgBox("Message Sent waiting for response"
'Sets Timeout to 60 second
objRequest.Timeout = 6000
'Gets the response back from the HTTP Post Reques
objResponse = CType(objRequest.GetResponse(), HttpWebResponse

ResponseCode = objResponse.StatusCod

'Reads the response back into Text forma
objReader = New StreamReader(objResponse.GetResponseStream(), Encoding.UTF8
ResponseMessage = objReader.ReadToEnd(
objReader.Close(

Catch e As Exceptio
MsgBox(e.Message & " " & e.InnerException.Message
End Tr
Return Tru
----- Nick Harris wrote: ----

Sample code might help. Generally when those types of issues arrive. Ther
is an issue with security permissions. Have you made any changes to you
machine.config
Are you using impersonation

Let me know

Nic
"Dave" <an*******@discussions.microsoft.com> wrote in messag
news:04****************************@phx.gbl..
I have developed a VB.net application that transfers
SOAP wrapped message to another server securely(using SS
and sever/client certificates). When I run this app fro
a Windows 2000 Professional box everything works a
expected, the secure channel is established and th
message is sent properly. When I use the exact same ap
on the Windows 2000 Server(running IIS) box the app doe
not work properly. I have used a packet sniffer to tr
and see what is going on and it appears the server canno
establish a secure connection with the remote server.(Al
the appropriate certificates are installed on both boxes
IS there some setting which needs to be changed in Window
2000 Server in order for this to work??? (I am logged int
the Windows 2000 Server as a client/ it is not running a
a service). I don't understand why this would work unde
Windows 2000 Profession and not under Windows 200
Server. Any help in resolving this issue would be greatl
appreciated. Thanks in advance


Nov 22 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.