As usual i'm in a pickle and have attempted to work it out for myself but failing. Any advice and help would be appreciative
After joining a XP PRO SP2 laptop to SBS 2003 network using http://
er, all fine and reboots twuice (creating the sb_instal profile) but will not logon on to the domain with any credentials and get errors saying domain not available etc.
server reports error netlogon 5722 Accerss is denied when attempting to logon from newly joined laptop.
The SBS server is inherited but I have maintained it for about 2 years now. Fully patched and only 4 machines on network. Have joined machines correctly through connectcomputer. Exchange sP2. Handles mail delivery for 2 domains and using PDA to sync with exchange using utilities in SP2.
Client document redirection enabled redirecting to default shared folder for users.
Laptop in question was running very slow so I gave it a good clean up. It then lost connectivity to server via VPN. VPN is not sbs but directly to watchguard firebox and works fine on other machines.
Brought laptop in to the office and connected on LAN, would not login to the domain. Researched netlogon 5722 and thought that profile on laptop corrupted. Rebuilt laptop from scratch and reinstalled applications. created machine account in wizard. Joined domain through connectcomputer.
machine rebooted twice. Would not logon to domain.
In AD Domains and Trusts then domain name is city123limited,local but th pre windows 2000 name is city123
In AD Sites and services the full name is server.city123limited.loca
When a machine joins the domain the domain in the logion box is listed as city123
Results of nltest that are puzzling me
I_NetLogonControl failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN
Dom Guid: 7fc6b60f-df84-4def-bef8-a0
Dom Name: city123
Forest Name: city123limited.local
Dc Site Name: Default-First-Site-Name
Our Site Name: Default-First-Site-Name
Flags: PDC GC DS LDAP KDC TIMESERV GTIMESERV WRITABLE DNS_FOREST CLOSE_S
The command completed successfully
From what I can see there seems to be an issue with the secure channel between newly joined machine and server but all google results bring me to issue with trusts in 2K and 2003 but this is a standalone SBS2003
Many thanks for taking the time to read this and I will respond as quickly as possible to any further questions athough my internet access is limited from tonight through to Sunday night.