Ghost 9 images on unreachable share

[HodgeHi]

Hello all,

 

I have got an old pc that doesn't support Ris'ing and have created a ghost image of a similar machine and placed it up onto the server share ready.

 

When I come to image the problem machine I cannot access the share.

 

I start the networking services and go through the motions until I browse for the image. I select the server and it gives me an access is denied error.

 

I then type in the direct link to the file and I get the error check your permisions on the network drive.

 

I have given Everyone read only rights (both on security and sharing) to the root of the drive right down to the location of the image and have also added the machine as well to the permissions.

 

Still it won't conenct.

 

What am I doing wrong? It must be something simple.

 

The server is 2k3 and machine is XPsp2, using Ghost 9

 

Thanks for any help.

[ChrisH]

If you are browsing to a share rather than taking part in some kind of image cast it might mean you will have to authenticate properly in this case with a known username.

[HodgeHi]

Yeah it asks for a username, and i authenticate as the admin for the domain but it fails to authenticate and says i need to check the permissions on the network. I used domain\username and just username but still no difference.

[ChrisH]

Maybe its a security issue then. Have you sucessfully logged on using a similar method before? The thing that nags at the back of my head is something like SMB signing which may be stopping you authenticate this way. This can be turned of in the default domain policy and you used to have to do it to get some of the 9x clients to authenticate on 2003 I think (or something of that nature).

[HodgeHi]

Its funny you should ask as it did used to work, but when we were running an NT4 domain.

 

The share resided on a W2k3 server but it was running under the NT4 domain and so would allow access. It may be what you say it is, SMB signing.

 

I have not heard of this before. I don't control the security setings for the domains.

 

Where would i find this setting?

[krisd32]

are you using ghost cast or the actual ghost product all mine seem to work using ghost cast!

 

failing that seems as it is only one machine why don't you just do a direct ghost from the other machine and then get a spare hard drive to put the image on to for time saving in the future only 2 screws and your in there.. just an idea

 

kris

[HodgeHi]

@krisd32

 

It is just the one machine but there are others that will need doing eventually, and so i was looking to leave it on the ris server with all the other images.

 

I am not ghost casting just imaging one at a time when needed.

 

I will more than likely use the HDD for a temporary measure but would like to resolve this issue. I don't like it when things aren't working correctly.

 

Thanks for the responses anyway.

[krisd32]

you can use ghost cast to image 1 at a time if you have it.

 

i have all my images for ghost on the root of a drive and ghost cast sets the permissions i presume. i'm not up to ris yet not enough time.

 

if you want help with ghost cast i'll gladly email you loads of manuals etc..

[HodgeHi]

That would be excellent if you could do that.

 

I only have around six machines at the moment that need to be ghosted but a good backup procedure in case the RIS fails.

 

I could create a ghost image of the ris images just in case.

[krisd32]

ok i'm not at the school at the moment but i'll pm you tommorow and either give you a link to a site or if i can find them email you the instruction i use wrote for ghost cast!

[Frazer]

There is a policy in 2K3 that stops insecure clients from authenticating (DOS), we had exact same problem!

..goes off to find it..

[plexer]

I'll wager that that is the problem I keep all my ghost images on my 2000 member server for this reason but soon everything will be 2k3 so I'll have to sort it out then.

 

Ben

[Geoff]

You could use a Linux box running Samba?

[Frazer]

On the domain controller set "Microsoft network server: Digitally sign communications (always)" to Disabled.

Start > Administrative Tools > Domain Security Policy > Security Settings > Local Policies > Security Options > in here!

 

Alternatively a member server (not a DC) _should_ work without disabling this setting (move the image there)

[HodgeHi]

Great!! Thanks for that i have just rebuilt the RIS server and demtoed it to just a member and not a DC.

 

I will try that ASAP.

 

..runs off to try..

[SpuffMonkey]

On the domain controller set "Microsoft network server: Digitally sign communications (always)" to Disabled.

Start > Administrative Tools > Domain Security Policy > Security Settings > Local Policies > Security Options > in here!

 

Alternatively a member server (not a DC) _should_ work without disabling this setting (move the image there)

 

Thats the one! It took us days to work it out when we first had 2003 - I'd forgotten that.