1

Both localhost and 192.168.0.199 both resolve to the same page in my web browser (they both redirect to localhost/xampp/ and 192.168.0.199/xampp/ respectively).

But when I try not to access my web service, localhost:49973/BaseballWebService/Service.asmx/ resolves the web service and 192.168.0.199:49973/BaseballWebService/Service.asmx/ cannot find the webservice.

I have to access my web service using my computers ip instead of localhost because I have to access the we service remotely over a local network. Anyone have an idea what could be going wrong?

Bryan
  • 149
  • 1
  • 3
  • 10
  • Could XAMPP be interfering with my web service port? The web service is launched from Visual Studio and is C# .NET? – Bryan Oct 24 '09 at 21:29

1 Answers1

2

Make sure that you aren't using 2 sites instead of 1. It's possible that you have 2 different sites that both have a /xampp folder but don't both have the BaseballWebService folder.

If a single site has both localhost (or 127.0.0.1) and 129.168.0.199 bindings then it must be something causing a redirect in the BaseballWebService folder. A good test is to create a test.txt or test.htm page and place it in your BaseballWebService folder to confirm that IIS is serving up that file correctly without redirecting.

I'm assuming that you're using IIS since you've tagged this as IIS.

Scott Forsyth
  • 16,339
  • 3
  • 36
  • 55
  • Thanks a lot Scott! I am not sure I am using IIS. I think it is the ASP.NET development server 9.0. I uninstalled XAMPP and now when I go to localhost/ I get the message: Forbidden You don't have permission to access / on this server. Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request. But I can view my web service at localhost:49973/BaseballWebService/Service.asmx/… – Bryan Oct 24 '09 at 22:33
  • 1
    I found my answer here: http://weblogs.asp.net/ryangaraygay/archive/2008/04/19/asp-net-development-server-cannot-be-accessed-using-non-localhost-url.aspx . On development server localhost access only, no ip access. So I need to fire up IIS. – Bryan Oct 24 '09 at 22:37
  • Good find. Glad you were able to track it down. As a side, you can set IIS sites for debugging in Visual Studio/Visual Web Developer. Edit the properties of the project to tie to the IIS site. – Scott Forsyth Oct 25 '09 at 04:09