Thanks for the reply lanwench ill post the ipconfig tommorow(monday).

The dns server on all the workstations and the server is set to
192.168.0.149 which is the static ip address of the server.

This configuration has been working fine for about 2 years with no logon
problems and access to the internet from all workstations. There has been no
configuration changes since about two weeks ago when a vpn was set up from a
branch office to the main office but this is all working fine. It was only
friday that it went pear shaped and all the problems started.

If i give a workstation the routers ip address for the secondary dns server
then i can access the internet but still cannot logon to the domain or join a
pc to the domain.

Thanks
Gareth

"Lanwench [MVP - Exchange]" wrote:

Gazza wrote:
I hope someone can help with a strange problem.

I have a windows 2003Std dc running ad and dns supporting about 20
users running winXP pro and am having severe issues when it comesx to
user logons.

When i tried to logon to the server from a client pc the logon seemed
to take forever and when it did eventually logon an error popped up
saying that they couldnt access there desktop(stored on the server as
a roaming profile(server\profiles) and folder
redirection(server\Users).

This has been working perfectly for about 2 years now and has just
suddenly stopped working.

I have checked dns on the server and all is well, the clients have the
server set as there primary dns server.

I am able to logon to the domain at the server and also connect to the
internet at the server but cannot do either at the client Pc`s.

I have run dcdiag and netdiag and there are no errors.

I can ping the server by IP address and name from the client pc`s and
can also connect to the administrative share (c$) on the server from
the clients.

Don`t know what else to try so am looking to the experts for help.

Thanks in advance
Gareth

Hi - if you post an unedited ipconfig /all from the DC and from a
workstation, it will help.

I note that you've mentioned "primary" DNS server - this indicates you've
got DNS configuration problems. Your internal DNS server should be the
*only* one the clients (pr server itself) specifies. No public IPs should be
present in an ipconfig /all from a server or workstation. You will have a
slew of unpredictable problems with AD if your DNS isn't set up properly.