Webservice on port 9999 vs2008

Why is your webservice pointing at vs2008.org? as far as I can see the domain does not exist.

jh71283 said:

Why is your webservice pointing at vs2008.org? as far as I can see the domain does not exist.

Well If he wanted to make it a public webservice then I am sure he would have used port 80 !!
and he would have given everyone and their dog the address to play with on port 80 and the question that he asked would not be a question , now thats what you call smart!!

SECURITY
SECURITY
SECURITY

a0011010011 there is a utility called Wsdl.exe

look here
http://msdn.microsoft.com/en-us/library/7h3ystb6(VS.80).aspx">http://msdn.microsoft.com/en-us/library/7h3ystb6(VS.80).aspx
try this
http://www.devcity.net/PrintArticle.aspx?ArticleID=24
http://www.devcity.net/PrintArticle.aspx?ArticleID=26

erictheman said:

jh71283 said:

*snip*

Well If he wanted to make it a public webservice then I am sure he would have used port 80 !!
and he would have given everyone and their dog the address to play with on port 80 and the question that he asked would not be a question , now thats what you call smart!!

SECURITY
SECURITY
SECURITY

a0011010011 there is a utility called Wsdl.exe

look here
http://msdn.microsoft.com/en-us/library/7h3ystb6(VS.80).aspx">http://msdn.microsoft.com/en-us/library/7h3ystb6(VS.80).aspx
try this
http://www.devcity.net/PrintArticle.aspx?ArticleID=24
http://www.devcity.net/PrintArticle.aspx?ArticleID=26

did you read the OP's error message ?? I do not think you did....  he has a reference to a domain name that is not resolved!

the port # is another issue.... 

and using a different port # is *NOT* a way to create security!

figuerres said:

erictheman said:

*snip*

did you read the OP's error message ?? I do not think you did....  he has a reference to a domain name that is not resolved!

the port # is another issue.... 

and using a different port # is *NOT* a way to create security!

Metadata contains a reference that cannot be resolved: 'http://vs2008.org/email-catcher/service.asmx?wsdl'.

where is the port 9999 here ?

should read 
Metadata contains a reference that cannot be resolved: 'http://vs2008.org:9999/email-catcher/service.asmx'.Unable to connect to the remote server

maybe you should try this out.........
it has nothing to do with domain name..............

its ports
further a0011010011 says clearly 
The webservice runs perfectly, via http://etc.service.asmx/
I see the webservice and am able to run it nicely,

And tell me about security ?
when is the last time you scanned port 9999 through all class a b and c addresses ?
when is the last time you scanned port 80 through all class a b and c addresses ?
what would you scan port 80 or 9999 ? hmm lets see .....
Basic security
like I said its a ports problem in visual studio 2008.......... I have just tried it with the same results so there.

erictheman said:

figuerres said:

*snip*

Metadata contains a reference that cannot be resolved: 'http://vs2008.org/email-catcher/service.asmx?wsdl'.

where is the port 9999 here ?

should read 
Metadata contains a reference that cannot be resolved: 'http://vs2008.org:9999/email-catcher/service.asmx'.Unable to connect to the remote server

maybe you should try this out.........
it has nothing to do with domain name..............

its ports
further a0011010011 says clearly 
The webservice runs perfectly, via http://etc.service.asmx/
I see the webservice and am able to run it nicely,

And tell me about security ?
when is the last time you scanned port 9999 through all class a b and c addresses ?
when is the last time you scanned port 80 through all class a b and c addresses ?
what would you scan port 80 or 9999 ? hmm lets see .....
Basic security
like I said its a ports problem in visual studio 2008.......... I have just tried it with the same results so there.

erictheass said:

I have just tried it with the same results so there.

Way to endear yourself.


When posting error messages, if you wish to remove your domains, at least make it obvious, such as changing it to tempuri.org or (domain removed).

I had assumed that the user had not changed the domain names as a security measure, considering that he has left the IP address that the domain name resolves to intact.

erictheass said:

Download:[Pending]

Metadata contains a reference that cannot be resolved: 'http://vs2008.org/email-catcher/service.asmx?wsdl'.

where is the port 9999 here ?

should read 
Metadata contains a reference that cannot be resolved: 'http://vs2008.org:9999/email-catcher/service.asmx'.Unable to connect to the remote server

maybe you should try this out.........
it has nothing to do with domain name..............

Newsflash: changing the error message does not correct the error.

jh71283 said:

erictheman said:

*snip*

Newsflash: changing the error message does not correct the error.

news flash if we learn to read the error message we can debug the problem.........

have you tried this ? or maybe your to busy looking for spelling mistakes !!! lol you have heard of IIS right ?
you do know how to create a port in IIS right, If you need I can send you a link on how to do it.

erictheman said:

jh71283 said:

*snip*

news flash if we learn to read the error message we can debug the problem.........

have you tried this ? or maybe your to busy looking for spelling mistakes !!! lol you have heard of IIS right ?
you do know how to create a port in IIS right, If you need I can send you a link on how to do it.

Eric. I'm not stupid, please don't assume that I am.

At which point did I indicate that I had not read the error message, and at which point did I point out any spelling errors?

My point was that you have changed the text of the error message as an example. that achieves nothing.

jh71283 said:

erictheman said:

*snip*

Eric. I'm not stupid, please don't assume that I am.

At which point did I indicate that I had not read the error message, and at which point did I point out any spelling errors?

My point was that you have changed the text of the error message as an example. that achieves nothing.

Hi there, Please put away the bats

No need for bloodshed

as I posted in my first post the webservice running on port 9999 works fine as I access it with internet explorer. the service runs fine and the webservice updates the database as expected using http, it is not a problem with DNS nor Domain name, Eric is right in that respect.
the problem comes in with visual studio 2003 -2005 -2008. If I attempt to attach the webservice the wizard reports that it is looking on port 80 and not on port 9999, it starts looking on port 9999 then switches of to port 80. It looks like visual studio "thinks" that all webservices should run on port 80 by default and starts to look there, after it gets the original url from the wizard.
Eric thank you for your input. ill look at those urls now.
And I did change the log details for security but please learn to be more patient you could have just ignored those posts and answered myn. But thank you anyway.

The only text that was changed was domain names and ip addresses, the error from the wizard is the same otherwise.

My question is simple do I have to use port 80 or can I use any port I want ? and if I can use any port i want how do I do it

Thanks to all , and stop fighting please.

I found this is a common problem that the solution no longer works in vs2008
http://www.tech-archive.net/Archive/DotNet/microsoft.public.dotnet.framework/2004-05/1885.html

Eric is this you ?
http://www.developer.com/services/article.php/3649576

a0011010011a said:

jh71283 said:

*snip*

Hi there, Please put away the bats

No need for bloodshed

as I posted in my first post the webservice running on port 9999 works fine as I access it with internet explorer. the service runs fine and the webservice updates the database as expected using http, it is not a problem with DNS nor Domain name, Eric is right in that respect.
the problem comes in with visual studio 2003 -2005 -2008. If I attempt to attach the webservice the wizard reports that it is looking on port 80 and not on port 9999, it starts looking on port 9999 then switches of to port 80. It looks like visual studio "thinks" that all webservices should run on port 80 by default and starts to look there, after it gets the original url from the wizard.
Eric thank you for your input. ill look at those urls now.
And I did change the log details for security but please learn to be more patient you could have just ignored those posts and answered myn. But thank you anyway.

The only text that was changed was domain names and ip addresses, the error from the wizard is the same otherwise.

My question is simple do I have to use port 80 or can I use any port I want ? and if I can use any port i want how do I do it

Thanks to all , and stop fighting please.

I found this is a common problem that the solution no longer works in vs2008
http://www.tech-archive.net/Archive/DotNet/microsoft.public.dotnet.framework/2004-05/1885.html

Eric is this you ?
http://www.developer.com/services/article.php/3649576

I tried adding a web service reference to a web service running on port 9999 and I don't see any problems (VS2008).  I'd suggest you to install Fiddler (http://www.fiddlertool.com/Fiddler2/version.asp) and see what VS is doing. The host header mentioned in the page you linked to is definitely correct here. My guess is that something is wrong on the server side, not in VS.

And in general: if the "add reference" wizard is giving you trouble for some reasons it doesn't mean you can't run the web service on a port other than 80. You can:
1. temporarily run the web service on port 80 just to add the reference. After adding the reference you can edit the URL in the generated files or simply set the Url property when you create an instance of the web service proxy.
2. get the wsdl file by using a browser and then use the wsdl.exe tool from the .NET SDK to generate the web service proxy.