Topic: Inbox problems

[michelandre]

Hi Paperguides,

I am not a Win$ guru but I think that 6) is the problem.

6) logon from web interface.  set remote access, windows domain name and domain controller.

I do not think that when you create a PDC with the same name as before that it will have the same number. The name will be the same but the internal representation will be different.

- The W10 station belong to the original domain (with the original name/number).
- You create a same "new" domain but W10 does not recognize the new server (with the original name/not orginal number).
- Human will not see the difference but computer will.

* You should give all right to everyone to the shared backup directory.
* Create the new server with same name and FQDN and IP as before. No domain. The FQDN is just to get to the sub-directory name (FQDN) in the shared directory on W10. Worse case, if you take a new name for the new server, just make sure to rename the sub-directory name with the new FQDN.
* Configure backup to point to the W10 shared directory.
* Restaure should work because everyone can get to the Shared dir.
* On reboot, everything will be as before (same name/same number)

My 2 1/2 cents

Michel-André

[Paperguides]

theorically speaking, Stefano is on vacations but

I hope you are having a good time.  My vacation isn't till late September.   Again my thanks for taking time to help me.

IMO, since your server is for you (one man band, IIUC), you have no contribs installed and few clients in your lan, you'd start from scratch..


- how many clients do you have in your lan?

None.  I'm trying to retire so all my commercial customers have been transferred to other IT Support companies.   After over 45 years of 'playing' with computers I've finally giving up the fight to keep up with technology.   Taken up completely different path.  www.thesilversworkshop.org.uk
 

- how many users in your server?

Just 4 of which only three of us are active.

- how much data in your server?

85G and I don't understand how.   I have a separate backup of this data.

your mails are not lost and they can be recovered quite easily, but you must exit from the SME way of doing things..

please answer to my questions above, tomorrow, depending on your answers, I'll suggest you how to proceed (gevie you a plan, then you'll decide if follow it)

I am happy to start from scratch if necessary but I would like to be able to get back the mail.

Regards,

Tony

[Paperguides]

I am not a Win$ guru but I think that 6) is the problem.

With the speed and regularity that Microsoft change the rules, who can be?

I do not think that when you create a PDC with the same name as before that it will have the same number. The name will be the same but the internal representation will be different.

I suspected that was the case but my understanding the way M$ deals with domains was never great.

* You should give all right to everyone to the shared backup directory.
* Create the new server with same name and FQDN and IP as before. No domain. The FQDN is just to get to the sub-directory name (FQDN) in the shared directory on W10. Worse case, if you take a new name for the new server, just make sure to rename the sub-directory name with the new FQDN.
* Configure backup to point to the W10 shared directory.
* Restaure should work because everyone can get to the Shared dir.
* On reboot, everything will be as before (same name/same number)

I was confused when I could not access the backup share as I deliberately gave 'everybody' full access.

My 2 1/2 cents

Michel-André

Thanks for joining in.

Regards,

Tony

[michelandre]

Hi Paperguides,

Reboot the W10 station and login as \\Administrator. You will not be loged in the domain, only into the station W10.

Do the same with another station and see if it can access the backup directory of W10 with Windows Explorer.

Michel-André