Shawn,
The CLSID in the registry & group policy (SYSVOL) etc will be different & so
maybe the DNS server IP
Is the DNS registered? Why didn't you restore AD, system state... from an
earlier backup? No backups then you don't value your users data... Bad
administration. Was the RAID rebuilt?
The DNS on the workstations seems to be holding the old DNS info & should be
flushed
Obviously, the network printers may have out-of-date IP/DNS and so on
information. Are they shared or pure network? If shared then they aren't
looking at the same server as the machine sees it not you
Awaiting your findings
--
SPAMCOP User
"Shawn Martin" <> wrote in message
news:...
>I do understand that this would not restore the Domain controller. I
>recreated the server with all the user accounts and the shares, restored
>the data. I tried to restore the domain controller through the backup but
>it didn't restore properly. All the data remained intact. I think the
>hardware was just too different. The scenario I described regarding
>network behavior happens everyday. So rebooting the workstation is
>temporary, the following day it would behave the same. Many workstations
>experience this situation.
>
> Printing, if I have a shared network printer using an IP port, and I
> create a local printer using the same IP port the local printer will
> behave properly no slow down.
>
> Marcin wrote:
>> Shawn,
>> just to clarify - does rebooting a workstation where you experience the
>> "slowness" resolves the issue (temporarily)? If so, this behavior would
>> typically indicate a memory leak on the workstation rather than
>> domain-wide issue...
>> On the other hand, your description raises some red flags - in
>> particular:
>> - reinstalling a domain controller with the same server and domain name
>> does not automatically provide replacement for a failed domain
>> controller. If this was the only domain controller in AD environment,
>> then reinstalling it essentially invalidates all of its content -
>> including all of its objects (users, groups, etc.)
>> - you indicate that local printing is faster than network printing. When
>> you refer to "local" vs. "network" - are you comparing a scenario where
>> someone prints to a printer physically attached to a computer
>> (parallel/USB) with a scenario where that printer is attached to network?
>> If so, you might want to also look into your network utilization...
>>
>> hth
>> Marcin
>>
>> "Shawn Martin" <> wrote in message
>> news:%...
>>> After a recent server crash I had to rebuild a new server. I created a
>>> domain controller with the same server name and domain name. On the
>>> workstations I removed them from the domain and they became a member of
>>> a workgroup. I then added them back as a member of the domain to
>>> rebuild the trust relationship.
>>>
>>> Most workstations also have several printers defined that are network
>>> printers. These network printers seem to slow the performance of the
>>> workstation compared to a local printer. Excel performance is much
>>> slower using a network printer as default. In the morning performance is
>>> not bad, as the day progresses into the late afternoon performance gets
>>> worse accessing a network share. Eventually the workstation is unable
>>> to access a network share and will need to be rebooted to access the
>>> network properly.
>>>
>>> Is there anything on the workstations that needs to be cleaned out
>>> referring to the old server?
>>>
>>> Thanks
>>
|
Similar Threads
Linear Mode
