[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference cookie::archive_backup

Title:	Archive/Backup

Moderator:	COOKIE::MHUAIG

Created:	Wed Sep 08 1993
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	479
Total number of notes:	2283

391.0. ""Service received request from unregistered server...event id 106"" by CX3PST::BSS::SAUL () Mon Mar 03 1997 12:39

Hi,

Customer is attempting to do a NT backup on 2.1.  This is what he
sees...

"When I run the save request the log file still says BSGTAR SERVER ACCESS
DENIED and the NT Event Log still says "..service received request from
unregistered server..." (Event ID 106)."


He can ping the server from the NT box.
The port number is set properly.
Client service is running.

Any ideas what to look for?

Thanks,

Ted

T.R	Title	User	Date	Lines
391.1	Check server name is registry	COOKIE::PETERS	`Mon Mar 03 1997 12:54`	12
	Have him check the registry entry for the ABS Client using REGEDT32. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ABSClient\Parameters Server REG_SZ nameofserver This value should have string with the name of his Server. This name is checked against the name recieved from ABS for security purposes. The port is definitly ok because the TCP/IP connection is getting established. Lyle
391.2		CX3PST::BSS::SAUL	`Tue Mar 04 1997 14:21`	10
	Customer reports this back: >I checked the Registry entries for the ABSclient Parameters and the server >entry is corrrect and pingable from the NT system. The IP address in the >key is also correct and pingable. The port is 1800, and matches the port >on the VMS/ABS Client License entry. The path points to a valid file. Any other suggestions? Thanks... Ted
391.3	Fully qualified name?	COOKIE::PETERS	`Wed Mar 05 1997 08:32`	5
	Does your customer have the fully qualified name of the server in the registry, such as "cookie.dec.com" or just the server name "cookie". If they are using the full name have them change it to just the server name itself. In the meantime, I'll start examining code paths for possible problems with the checking code. Lyle
391.4		CX3PST::BSS::SAUL	`Wed Mar 05 1997 11:21`	6
	Hi Lyle, Yes, he has tried it both ways...uppercase, lowercase, full domain name and just the server name. Ted
391.5	Questions and Workaround	COOKIE::PETERS	`Thu Mar 06 1997 15:18`	27
	A couple of questions? 1) When your customer was making changes to the registry did they issue a STOP/START NT Service Manager command between each modification? The service only reads the registry on startup and shutdown. 2) If 1) is yes and there are still problems. - What version of ABS? (ABS V2.1 or ABS OMT) - What version of UCX on the server? - What version of NT and service packs installed? - TCP/IP properties defined on the client: IP Address: Using DHCP or specific IP addressing. DNS: Using DNS server WINS: Using WINS server or letting DNS resolve Using LMHOSTS Routing: Is IP routing enabled Workaround: Under the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ABSClient\Parameters Add the value: Authentication REG_DWORD 0 This turns off authentication of the server. Setting the value to 1 will reenable the authentication.
391.6		CX3PST::BSS::SAUL	`Mon Mar 10 1997 15:57`	25
	From the customer: >To answer you questions: > >1. We have not changed the registry entries for ABS, we go through the > ABS SETUP each time we try a new server node name. > >2. The NT Client software identifies itself as ABS OMT. > UCX on the server is v3.3 eco 10 > NT version is 3.51 Workstation (I do not know about service packs) > We are not using DHCP, we use specific addresses > Addresses are resolved by DNS > IP routing is enabled > >We were able to get this problem resolved by using the node name from DNS >of the FDDI address for the server. The server has a node name for the >primary ethernet connection, the secondary ethernet connection, and the >FDDI connection. The NT system we were attempting to back up in not on >FDDI, but ABS is going out on the FDDI at the server and getting routed into >ehternet to get to the PC. The requesting server name then appeared to be >the name associated with the FDDI port on the server. > >We were able to do the backup, but restores are now a problem. This will be >the subject of a new problem.