Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

dns command line name win2k

Status
Not open for further replies.

derson

MIS
Oct 2, 2002
73
GB
does anyone know the command line name for dns client so i can stop/start it in a batch file
many thanks
 
Which dns client? Which OS Win2K Linux?
 
nope tried that and every cobo i could think of but no joy..can you use that command?
 
found it it's DNSCACHE
thanks for your responses
derson
 
Yup, it works for me:

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\Documents and Settings\Administrator>net stop "DNS Client"
The DNS Client service is stopping.
The DNS Client service was stopped successfully.


C:\Documents and Settings\Administrator>net start "DNS Client"
The DNS Client service is starting.
The DNS Client service was started successfully.


C:\Documents and Settings\Administrator>
 
me too-not thinking due to stress of problem!! thanks for your help by the way my prolem is I am having a fairly big problem- dsaccess seems to fail every 1.5 hrs which of course causes failure of services and therfore no access for users, backups fail overnite etc.......stopping and starting dns client resolves it temporarily can anyone help a)fix properly and b) temp how do i stop/start dns client from cl -i've tried net stop dns client etc no joy this way i could write batch file etc..BTW win2k sp2 e2k sp1 one DC one exchange box-dont spose you can help??
derson
 
Check my previous posting on how to stop/start dns client from command line.
 
Are ther any error messages in your event logs?
 
some event msgs taht are relevant:
or more information, click 04/06/2003 16:49:03 MSExchangeDSAccess Error None 2064 N/A EXCHANGE Process MAD.EXE (PID=2104). All the remote DS Servers in use are not responding.

For more information, click 04/06/2003 16:47:35 Userenv Error None 1000 NT AUTHORITY\SYSTEM EXCHANGE Windows cannot determine the user or computer name. Return value (1722).
04/06/2003 16:43:02 MSExchangeDSAccess Error None 2064 N/A EXCHANGE Process MAD.EXE (PID=2104). All the remote DS Servers in use are not responding.

For more information, click 04/06/2003 16:43:00 MSExchangeDSAccess Warning None 2070 N/A EXCHANGE Process MAD.EXE (PID=2104). Dsaccess lost contact with domain controller sabanci-pdc.Sabanci. Error was 80040934. Dsaccess will attempt to reconnect with this domain controller when it is reachable.

For more information, click 04/06/2003 16:28:35 MSExchangeFBPublish Error General 8213 N/A EXCHANGE System Attendant Service failed to create session for virtual machine EXCHANGE. The error number is 0xc007052e.

For more information, click 04/06/2003 16:03:35 MSExchangeFBPublish Error General 8213 N/A EXCHANGE System Attendant Service failed to create session for virtual machine EXCHANGE. The error number is 0xc007052e.

For more information, click 04/06/2003 15:56:42 ESE98 Information Logging/Recovery 210 N/A EXCHANGE Information Store (2960) The instance 14d37532-e426-4d90-8067-d06d298b722b is starting a full backup.

For more information, click 04/06/2003 15:38:35 MSExchangeFBPublish Error General 8213 N/A EXCHANGE System Attendant Service failed to create session for virtual machine EXCHANGE. The error number is 0xc007052e.

For more information, click 04/06/2003 15:24:37 MSExchangeDSAccess Warning None 2070 N/A EXCHANGE Process MAD.EXE (PID=2104). Dsaccess lost contact with domain controller sabanci-pdc.Sabanci. Error was 80040951. Dsaccess will attempt to reconnect with this domain controller when it is reachable.

For more information, click 04/06/2003 15:13:35 MSExchangeFBPublish Error General 8213 N/A EXCHANGE System Attendant Service failed to create session for virtual machine EXCHANGE. The error number is 0xc007052e.

For more information, click
 
Is the server that you are getting these errors on your dns server as well?
 
just the exchange sever nothing on the dns box and i've enabled logging for everything relevant??
 
Verify that your dns settings for the exchange box are correct because these errors are generally caused by a dns failure.
run an ipconfig /all
and nslookup from a command prompt on your exchange server and make sure that your dns server is in the primary dns server location and that nslookup uses your dns server.
 
yep done that and all seems fine nslookup brings up dns server then if you put in exchange box by nhame or ip it is resolved- i agree that it is dns but where?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top