I've managed to manually fix the problem by specifying the machineName property for the http channel in the config file. Still, I'm not really happy with having to do it manually (or even doing it programatically) - is there anyway to get remoting or IIS to simply use the same IP or address as the initial request to the well-known object?
- [ADVANCED-DOTNET] 403 Forbidden for IIS Hosted Remote Object Andy Knowles
- Re: [ADVANCED-DOTNET] 403 Forbidden for IIS Hosted Remot... Andy Knowles
- Andy Knowles
