[gptalk] Re: A marginal problem

If this is Windows 2003 then you need to disable strict name checking;
http://support.microsoft.com/kb/281308 has details.

 

We have done this for a number of servers and I can confirm that it will
do what you want.

 

Steve

 

From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
On Behalf Of DinhDuy
Sent: 31 August 2007 05:14
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: A marginal problem

 

I create a CNAME but not successful.

 

 

From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
On Behalf Of Darren Mar-Elia
Sent: Friday, August 31, 2007 11:08 AM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: A marginal problem

 

How about a CNAME in DNS? Although Din, this doesn't really have
anything to do with Group Policy.

 

Darren

 

 

From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
On Behalf Of DinhDuy
Sent: Thursday, August 30, 2007 9:05 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] A marginal problem

 

Dear all, 

I have an application and it's data located on NAMESERVER. All Clients
run app client and access data on NAMESERVER. Now I want to remove
NAMESERVER out of my network. I move app data on NAMESERVER to
FILESERVER and then all app client can't access app data on FILESERVER.
I can't adjust the path in app client to point to FILESERVER. How can I
configure a fake computer name (NAMESERVER) on my network so that app
client can access to FILESERVER via a fake computer name - NAMESERVER. 

Please help me! 
Thanks in advance

Other related posts: