.NET Remoting requires "transparent" or "pass-through" authentication when network communication is directed through a proxy server. If the user is prompted to enter credentials when accessing the Internet, then you know the proxy server is not currently configured to use a pass-through authentication such as Windows Authentication or Active Directory.
Typically a Windows operating system is configured to use a proxy server for Internet access by using Internet Explorer's "Connections" settings (described below) or you can configure the client application's IdeaBlade.ibconfig file.
If Internet Explorer is already configured with the proxy settings, then you donít have to do anything since .NET Remoting inherits these settings. You can check the proxy information in Control Panel > Internet Options. An "Internet Properties" window opens, then click on the "Connections" tab, click the "LAN Settings..." button, check the "Use a proxy server..." checkbox and enter the computer name (or IP address) of the proxy server and the port used for outbound Internet traffic (http).
If you do not use the IE method, then there are 2 elements of the IdeaBlade.ibconfig file that must be used: <ProxyName> and <ProxyPort>. In the graphic below, I have circled the proxy elements in a blank ibconfig. You would replace "ServerName" with the computer name of the proxy server and you enter the port number configured on the proxy server that accepts client connections to the Internet for http traffic. Typically the port is 80 or 8080, but a custom port could be used instead. Of course, the rest of the standard "Remoting" elements need to be configured as well (I have not done that in the screenshot below):