Hi all,
I have experienced a problem with an application (Crystal Reports 9) after migrating a few PC's from a Window NT4.0 domain to a Windows 2000 domain.
The problem i believe lies in the application referencing the host name of the PC prior to changing to the Win2k domain ie:
computer1 (NT4.0) => computer1@abc.com.au (Win2K)
The application has a database that holds the host name for the PC from the time that the application was installed. Hacking this isn't really an option.
Is there a way to change the name of the pc (locally) so it is not a FQDN and have it continue to successfully work on the Win2K domain?
I haven't had much luck searching on the net.
Thanks in advance
I have experienced a problem with an application (Crystal Reports 9) after migrating a few PC's from a Window NT4.0 domain to a Windows 2000 domain.
The problem i believe lies in the application referencing the host name of the PC prior to changing to the Win2k domain ie:
computer1 (NT4.0) => computer1@abc.com.au (Win2K)
The application has a database that holds the host name for the PC from the time that the application was installed. Hacking this isn't really an option.
Is there a way to change the name of the pc (locally) so it is not a FQDN and have it continue to successfully work on the Win2K domain?
I haven't had much luck searching on the net.
Thanks in advance