Last post Oct 14, 2014 08:43 AM by Siva Krishna Macha
Oct 10, 2014 05:06 PM|sosume|LINK
Our network administrator set up rules in our firewall to allow our web site vendor to hit a web service that i wrote. Unfortunately, our network guy passed away. However, we have not altered the rules so, it should still work. I have VS 2013 using IIS
for its host but when i run our vendor's development web site, it is not hitting my web service. This is way out of my area of expertise. Anyone know how to get this set up properly and figure why it is not working?
Oct 11, 2014 01:22 AM|Siva Krishna Macha|LINK
Can you browse your "web service's url" from the "server" where your vendor's website is running?
Also, I'm assuming it is .asmx webservice. (not WCF svc).
Oct 13, 2014 10:24 PM|Shawn - MSFT|LINK
Based on your description, first you could check whether you could get the service description information when you access to the web service address in the vendor's client web browser.
If yes, it means the service hosts fine. And problem occurs on the vendor's client side. And you could check the whether the service reference added successfully, update the service reference, check the client service url reference etc..
If no, it says you can not access to the service. So, check the firewall settings(also with port), or redeploy the service in the server side.
Oct 14, 2014 08:43 AM|Siva Krishna Macha|LINK
Few more things you could check out:
1. Was there any changes in the webservice later, which could cause mismatch of your service's proxy at vendor site - as your service has latest version.
2. Vice-versa: Was there any changes in the vendor development server - may be the .NET framework version or IIS or any other software upgrades which could cause some settings changed.
3. If there is no change in server as well as in client side, check if you are able to access the "service url" from vendor development server. If you are not able to access, then that could be network or firewall issue as you mentioned.