Ghost Solution Suite

I have created a drive mapping boot package for our new dell laptops using the ndis dos driver package for the network card. All is Ok except when trying to map to a shared resource, where i get the access denied message. We have a windows 2003 environment and this process use to work ok. Not sure if somthing has changed in the windows environment, there seems to be quite a few people who are experiencing the same thing yet i cannot find one that has been able to resolve this issue. Any ideas anyone?

Hi Theodoros,

There were couple of discussions in the forum about this issue. Could you see if they are going to help you?

https://forums.symantec.com/syment/board/message?board.id=109&message.id=3766

https://forums.symantec.com/syment/board/message?board.id=109&message.id=4939


Krish

Kris,
Thank you for your reply, yes I have looked at these threads and tried the suggested, but they did not work, one point is that we have used windows 2003 servers in a domain environment in the past to run out images to new machines.
So I went back to the creating of my boot disk using ghost boot wizard, and changed the domain name in the client settings dialog box to workgroup (not our domain name) and it is now working, I am able to map to both my ghost and image directories.

perhaps an explanation would be useful from you guys...

regards

Hi Theodoros,

Good to hear your issue is resolved!

When we create the Drive Mapping Boot disk, all we do is populate these values in the system.ini file. It is similar to creating it manually and editing it. So it is difficult for me to think what the reason is.

It could be the way your policies are setup. I still think it is related to NTLM, but when you use a Domain account, server need to authenticate the user from the Domain. May be it is expecting a higher version of NTLM in that case. But if it is a workgroup machine, server could authenticate locally.

I'm not sure if this answers your question, but that's what comes to my mind.

Krish