Hi,
This probably happens because you use a DNS server that does not know about
your AD. You must use your domain controller as a DNS server for correct
name resolution for domain resources.
Leif
>I currently have a small network server that runs W2K server and Exchange
>2k
[quoted text clipped - 18 lines]
> Any
> suggestions Sorry for the length but I wanted to be as clear as possible
Patrick Brennan - 25 Sep 2006 23:09 GMT
> Hi,
>
[quoted text clipped - 28 lines]
>
> They are managed on the same server. Could you give me some suggestions for further resolution. Why does everything work on reboot. Do you think the new Sonice wall is interfering with DNS service. Or could you direct me to some articles to read. Everything has worked great for the last 2 years since I installed the services
Leif Pedersen [MVP] - 28 Sep 2006 21:41 GMT
Hi,
Still pretty sure that this is a DNS issue. Is the domain controller
pointing to itself as a DNS server and the configured with DNS forwarders.
Try to run dcdiag and netdiag on the domain controller - both of these tools
are part of the support tools which are on the 200x cd.
Leif
>> Hi,
>>
[quoted text clipped - 40 lines]
>> me to some articles to read. Everything has worked great for the last 2
>> years since I installed the services
>I currently have a small network server that runs W2K server and Exchange
>2k
[quoted text clipped - 5 lines]
> DHCP service as I only have 7 clients and the DHCP scope on the server has
> been removed.
You don't have to use your Windows box as the DHCP server, but it tends to
work a lot better. Make sure the DHCP scope on your Sonicwall is set up
properly - this includes the DNS suffix (yourlocaldomain.com), WINS (if you
use that, which you probably ought to), and DNS (pointing only at the
internal DNS server IP, *not* any public ones).
Since then some of my users must a reboot the workstatioin as
> they keep losing access to network shares. When the users lose printing
> cababilities for example or get the message the exchange server is not
[quoted text clipped - 8 lines]
> Any
> suggestions Sorry for the length but I wanted to be as clear as possible
I agree with Leif that this is most likely a DNS problem. Try posting an
unedited ipconfig /all from both the server, and a problem client.