Jump to content

tparad

Members
  • Posts

    4
  • Joined

  • Last visited

Reputation

0 Neutral

About tparad

Personal Information

  • Occupation
    Sys admin
  • Location
    Israel

Employer (optional)

  • Company Represented
    PAIS
  1. sorry to wake an old post but i just wanted to add the little line here. you wanted to delete the old's year shares and make new ones. no problem.. logon script net use * /del /yes net use X: \\server\Doc1 net use S: \\server\Doc2 net print \\server\printer1 net print \\server\printer2
  2. 12 hours yes, but then 12 more left. (original time is 24 not 12) so if the computer is offline for 24 hours that might be enough to delete it if savaging is timed to do so before the computer is online again. also... u wanted to automate a task. How to schedule computer to shut down at a certain time in the night. - Microsoft Community How to Automatically Shut Down Your Computer at a Specified Time i'm pretty sure you can have the user asked to click "not now" thingy so it won't shut down unless no respond for 60 seconds.
  3. Preferred is static ip. i'd advise only 1 DHCP server on a network, i hope that's not causing the duplicate IPs. with right configuration it is possible to run more ofcurse.. DHCP leases don't work that way, they re-check validation every half a time. for ex: if your lease time is 8 hours, the computer is the owner of the IP for the next 8 hours. after 4 hours (half the time) the DHCP validate the computer. In case still online - renews the lease time to 8 hours. means, if u obtain a new IP at 8 AM, and turns the computer off at 4:05 PM. obtain: 8 AM renew: 12pm renew: 4 pm lease time then will be 8 hours from 4 PM >> 12 AM. /EDIT if the computer is offline the timer is keep counting and again half the time that is left - recheck. lease 8 hours recheck 4 hours - offline recheck 2 hours - offline recheck 1 hour - online > back to 8 hours. recheck after 4 hours. EDIT/ if it's 24 hours you can already see. in other words, lease time should be 8 days. depends on the network setup and usage, those are just defaults \ recommanded. (DHCP>Scope>Right click - Options > under General) You havn't check DNS error logs
  4. Hi, 1. have you tried to rebuild the DNS zone? seems to fix some issues from time to time. 2. have you tried to re-configure the DHCP scope? there is an option with a command to export the settings so you won't miss anything when u re-configure. sometimes when the server runs for some time, we go in and make changes which doesn't always effect right-on and are silent. hope one of these or both, fix your issue for the long range. please post back. also one more thing, please review DNS errors in the Event viewer of the server and post back with -any- errors. screen shots are most welcome - or a fixed issue kobi
×
×
  • Create New...