On Apr 23, 4:34=A0pm, "Paul Calderon" <pcalder...@gmail.com> wrote:
> I'm developing an web application with DCOM interfaces.
>
> When I run the application from VS2005 (internal Web Server), I don't have=

> any problem accessing to the DCOM hosted by another machine.
>
> When I run the application from a virtual directory configured in IIS 7
> (Windows Vista), I can access too without problems.
>
> But When I run the application from a virtual directori configured in IIS6=

> (Windows 2003 Server), I can't access to the DCOM machine.
>
> I try everything, same users and passwords, same workgroup, etc, but the
> problem is just with IIS6.
>
> Any suggestion

On Apr 23, 4:34 pm, "Paul Calderon" <pcalder...@gmail.com> wrote:
> I'm developing an web application with DCOM interfaces.
>
> When I run the application from VS2005 (internal Web Server), I don't have
> any problem accessing to the DCOM hosted by another machine.
>
> When I run the application from a virtual directory configured in IIS 7
> (Windows Vista), I can access too without problems.
>
> But When I run the application from a virtual directori configured in IIS6
> (Windows 2003 Server), I can't access to the DCOM machine.
>
> I try everything, same users and passwords, same workgroup, etc, but the
> problem is just with IIS6.
>
> Any suggestion

On Apr 24, 7:35=A0am, "Paul Calderon" <pcalder...@gmail.com> wrote:
> I have 3 Machines
>
> Machine 1 (DCom Container) Windows 2003 Server
>
> Machine 2 (Web App Container) Windows 2003 Server
>
> Machine 3 (Developer Machine) Windows Vista
>
> Machine 1 have just the components we need to access from network (GIS
> Components)
>
> Machine 2 have the website over IIS6 (can't access to the Machine 1
> components), but if i run from Visual Studio there, the components are
> accesible.
>
> Machine 3 have a copy of the site over IIS7 (Vista), and there is no
> problem, when I run in Visual Studio, the components are accesible too
>
> All the firewalls are disabled.
>
> In this scenario we have 3 web servers, (IIS6, IIS7 and Visual Studio Web
> Server), I think is the way how each server try to connect to machine1, I'=
m
> using the same impesonalization from the 3 webservers, but I have problems=

> just with IIS6
>
> Any other suggestion
>
> "David Wang" <w3.4...@gmail.com> escribi=F3 en el mensaje de noticiasnews:=
b5758e81-4633-4ea0-b43e-1b371aca5df7@j33g2000pri.googlegroups.com...
> On Apr 23, 4:34 pm, "Paul Calderon" <pcalder...@gmail.com> wrote:
>
> > I'm developing an web application with DCOM interfaces.
>
> > When I run the application from VS2005 (internal Web Server), I don't ha=
ve
> > any problem accessing to the DCOM hosted by another machine.
>
> > When I run the application from a virtual directory configured in IIS 7
> > (Windows Vista), I can access too without problems.
>
> > But When I run the application from a virtual directori configured in II=
S6
> > (Windows 2003 Server), I can't access to the DCOM machine.
>
> > I try everything, same users and passwords, same workgroup, etc, but the=

> > problem is just with IIS6.
>
> > Any suggestion
>
> This does not look like an IIS6 problem because it does nothing
> special for or against DCOM.
>
> You need to start looking at what is different between the machines
> and your requirements of DCOM.
>
> For example, is the firewall enabled on Windows Server 2003. DCOM can
> require additional inbound ports which if denied by the firewall
> causes failures, and the Windows Server 2003 firewall is very
> restrictive.
>
> And on what OS are you running the VS 2005 test? Windows Server 2003
> or some other OS?
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> //

On Apr 24, 7:35 am, "Paul Calderon" <pcalder...@gmail.com> wrote:
> I have 3 Machines
>
> Machine 1 (DCom Container) Windows 2003 Server
>
> Machine 2 (Web App Container) Windows 2003 Server
>
> Machine 3 (Developer Machine) Windows Vista
>
> Machine 1 have just the components we need to access from network (GIS
> Components)
>
> Machine 2 have the website over IIS6 (can't access to the Machine 1
> components), but if i run from Visual Studio there, the components are
> accesible.
>
> Machine 3 have a copy of the site over IIS7 (Vista), and there is no
> problem, when I run in Visual Studio, the components are accesible too
>
> All the firewalls are disabled.
>
> In this scenario we have 3 web servers, (IIS6, IIS7 and Visual Studio Web
> Server), I think is the way how each server try to connect to machine1,
> I'm
> using the same impesonalization from the 3 webservers, but I have problems
> just with IIS6
>
> Any other suggestion
>
> "David Wang" <w3.4...@gmail.com> escribió en el mensaje de
> noticiasnews:b5758e81-4633-4ea0-b43e-1b371aca5df7@j33g2000pri.googlegroups.com...
> On Apr 23, 4:34 pm, "Paul Calderon" <pcalder...@gmail.com> wrote:
>
> > I'm developing an web application with DCOM interfaces.
>
> > When I run the application from VS2005 (internal Web Server), I don't
> > have
> > any problem accessing to the DCOM hosted by another machine.
>
> > When I run the application from a virtual directory configured in IIS 7
> > (Windows Vista), I can access too without problems.
>
> > But When I run the application from a virtual directori configured in
> > IIS6
> > (Windows 2003 Server), I can't access to the DCOM machine.
>
> > I try everything, same users and passwords, same workgroup, etc, but the
> > problem is just with IIS6.
>
> > Any suggestion
>
> This does not look like an IIS6 problem because it does nothing
> special for or against DCOM.
>
> You need to start looking at what is different between the machines
> and your requirements of DCOM.
>
> For example, is the firewall enabled on Windows Server 2003. DCOM can
> require additional inbound ports which if denied by the firewall
> causes failures, and the Windows Server 2003 firewall is very
> restrictive.
>
> And on what OS are you running the VS 2005 test? Windows Server 2003
> or some other OS?
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> //