Windows 2000, IIS, and ASP
-
I have an ActiveX control that works fine with my asp web application on Windows NT 4.0 servers and workstations. However, when moving the asp web application to Windows 2000, the control stops working. Internally, the control has to make Tuxedo connection to a backend server. Tuxedo is an old BEA middle-ware product that is based on TCP socket. The problem is that the socket connection always fails within my asp web application. However, the same control works fine on Windows 2000 machines if it is used outside of the asp web application. What I would like to know is, is there any setting in IIS (on Windows 2000) that will prevent socket connections to be established from asp web applications to other servers. Any help is appreciated. Thanks.
-
I have an ActiveX control that works fine with my asp web application on Windows NT 4.0 servers and workstations. However, when moving the asp web application to Windows 2000, the control stops working. Internally, the control has to make Tuxedo connection to a backend server. Tuxedo is an old BEA middle-ware product that is based on TCP socket. The problem is that the socket connection always fails within my asp web application. However, the same control works fine on Windows 2000 machines if it is used outside of the asp web application. What I would like to know is, is there any setting in IIS (on Windows 2000) that will prevent socket connections to be established from asp web applications to other servers. Any help is appreciated. Thanks.
-
I have an ActiveX control that works fine with my asp web application on Windows NT 4.0 servers and workstations. However, when moving the asp web application to Windows 2000, the control stops working. Internally, the control has to make Tuxedo connection to a backend server. Tuxedo is an old BEA middle-ware product that is based on TCP socket. The problem is that the socket connection always fails within my asp web application. However, the same control works fine on Windows 2000 machines if it is used outside of the asp web application. What I would like to know is, is there any setting in IIS (on Windows 2000) that will prevent socket connections to be established from asp web applications to other servers. Any help is appreciated. Thanks.
I think that you need to check your application configuration options. In ISM, Right click the name of your site/application choose "properties", Choose "Home Directory" Tab, under the "Application Settings" area, "Execute Permissions", change the drop down to "Scripts Only" and see if that helps, if not change to "scripts and executables" and see if that helps. You might want to restart IIS after each change to be sure that the new setting gets effected. Let me know what if this helps. - sage