Help - Domain just gone to pot, i cant explain it! :(

Hi everyone, I have a small Win2k3 domain running, there are 5 win xp
clients, a linux machine and a network attached SAN device (buffalo
terastation).

Recently, the past 2 weeks every machine except for the domain controller
takes 15-20 seconds to access. I can't explain it and it is hampering the
entire network, namely because all the user files are stored on the SAN
which itself takes 15-20 seconds to access EVERY time you need to access it.

What can I do, DHCP is setup correctly, i presumed DNS was setup correctly
(however I dont know how to check, advice welcomed here), in a bid to help
resolve issues I have setup WINS, again no changes in speed.

The domain controller is pretty speedy at connecting to clients, except for
the NAS device which is slow all round. Im just baffled, the network has
worked perfectly without change for months (it was rock solid for 6 months).

On the server 2 months ago i installed the .NET framework and MSMQ's and
addeded sharepoint, however this didn't cause any issues there and then,
could it be doing something now?

There is absolutely no information within the event viewier. Please, can
anyone offer advice as to the cause of the problem, anything I can do to
check my network settings, Windows domain settings, I can post ethereal
snifs if anyone with experiance would be kind enough to look at them.

Im absolutely stumped and really really confused and pretty much upset

Please, help, what can I do to check things out.

Thanks to all,
Kind Regards
Taz

Usually this is a DNS problem.

Basic AD DNS set up is:
AD must have a DNS server set up for the AD domain. It should point to
itself for DNS in the properties of TCP/IP.
All AD clients must point to the DNS server set up for the AD domain only.
For Internet access set up your AD DNS server to forward requests and list
your ISP's DNS servers as the forwarder or use root hints. This would be the
only place on your AD domain your ISP's DNS server should be listed.

What DNS server do your AD clients point to for DNS?


hth
DDS W 2k MVP MCSE

"Tarun Mistry" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi everyone, I have a small Win2k3 domain running, there are 5 win xp
> clients, a linux machine and a network attached SAN device (buffalo
> terastation).
>
> Recently, the past 2 weeks every machine except for the domain controller
> takes 15-20 seconds to access. I can't explain it and it is hampering the
> entire network, namely because all the user files are stored on the SAN
> which itself takes 15-20 seconds to access EVERY time you need to access
> it.
>
> What can I do, DHCP is setup correctly, i presumed DNS was setup correctly
> (however I dont know how to check, advice welcomed here), in a bid to help
> resolve issues I have setup WINS, again no changes in speed.
>
> The domain controller is pretty speedy at connecting to clients, except
> for the NAS device which is slow all round. Im just baffled, the network
> has worked perfectly without change for months (it was rock solid for 6
> months).
>
> On the server 2 months ago i installed the .NET framework and MSMQ's and
> addeded sharepoint, however this didn't cause any issues there and then,
> could it be doing something now?
>
> There is absolutely no information within the event viewier. Please, can
> anyone offer advice as to the cause of the problem, anything I can do to
> check my network settings, Windows domain settings, I can post ethereal
> snifs if anyone with experiance would be kind enough to look at them.
>
> Im absolutely stumped and really really confused and pretty much upset
>
> Please, help, what can I do to check things out.
>
> Thanks to all,
> Kind Regards
> Taz
>

> Basic AD DNS set up is:
> AD must have a DNS server set up for the AD domain. It should point to
> itself for DNS in the properties of TCP/IP.
> All AD clients must point to the DNS server set up for the AD domain only.
> For Internet access set up your AD DNS server to forward requests and list
> your ISP's DNS servers as the forwarder or use root hints. This would be
> the only place on your AD domain your ISP's DNS server should be listed.
>
> What DNS server do your AD clients point to for DNS?

Hi Danny, DNS is setup correctly. nslookups are flawless from any machine on
the network. I was running AVG on my network, i have now removed this from
my server and it appears things are coming back up.

Secondly, the buffalo runs on a cut down version of Linux, it doesnt
integrate into AD at all, i thought i had figured out a way to enable it
todo so, apparently not, what i dont get is that it worked for so long, what
has happened now to make the setup spit out its dummy? Anywho, i placed the
NAS device into its own workgroup, it now appears to be working.

Thanks again, any insight into this would be really helpful. AVG antivirus
to blame??

Thanks,
Taz