G
Gravy
Hi,
I have a client that we have written an intranet asp.net application for.
They installed it and configured it on some new hardware. The hardware was
configured as a real domain with new client machines. Everything was working
fine until...
The new hardware was then moved to a new office and everything transfered to
a new domain. The web server is not the domain controller. All that happened
to the web server was a domain change AND the network admin added a second
network card (for administration!).
Now, whenever they browse to the asp.net application they get an error page
that says: Server Application Unavailable.
Is it possible that the addition of the second network card screwed things up.
They are running Windows 2003 Server and .NET 1.1
Hope someone can help me
Regards
I have a client that we have written an intranet asp.net application for.
They installed it and configured it on some new hardware. The hardware was
configured as a real domain with new client machines. Everything was working
fine until...
The new hardware was then moved to a new office and everything transfered to
a new domain. The web server is not the domain controller. All that happened
to the web server was a domain change AND the network admin added a second
network card (for administration!).
Now, whenever they browse to the asp.net application they get an error page
that says: Server Application Unavailable.
Is it possible that the addition of the second network card screwed things up.
They are running Windows 2003 Server and .NET 1.1
Hope someone can help me
Regards