A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » Networking and the Internet with Windows XP
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

domain problem.



 
 
Thread Tools Display Modes
  #1  
Old February 14th 09, 01:20 PM posted to microsoft.public.windowsxp.network_web
Gazza
external usenet poster
 
Posts: 23
Default domain problem.

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
Ads
  #2  
Old February 14th 09, 05:55 PM posted to microsoft.public.windowsxp.network_web
Robert L. \(MS-MVP\)[_383_]
external usenet poster
 
Posts: 1
Default domain problem.

You may want to check the group policy. First use gpresult to see which
group policy apply the computer.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"Gazza" wrote in message
...
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


  #3  
Old February 14th 09, 05:55 PM posted to microsoft.public.windowsxp.network_web
Robert L. \(MS-MVP\)[_453_]
external usenet poster
 
Posts: 1
Default domain problem.

You may want to check the group policy. First use gpresult to see which
group policy apply the computer.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"Gazza" wrote in message
...
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


  #4  
Old February 14th 09, 07:10 PM posted to microsoft.public.windowsxp.network_web
Gazza
external usenet poster
 
Posts: 23
Default domain problem.

Thanks for the reply robert ill have to check that out on monday.

The other thing i forgot to put in the first post was the error message i
get if i try to add a client to the domain.

The Server cannot carry out the request(Something along those lines am not
at work now to check it sorry)

And also the computer that im joining shows up in the computers container
but is disabled and it doesnt seem to be joined at the client side(no domain
list at logon screen.

Thanks again
Gareth
  #5  
Old February 14th 09, 07:10 PM posted to microsoft.public.windowsxp.network_web
Gazza
external usenet poster
 
Posts: 23
Default domain problem.

Thanks for the reply robert ill have to check that out on monday.

The other thing i forgot to put in the first post was the error message i
get if i try to add a client to the domain.

The Server cannot carry out the request(Something along those lines am not
at work now to check it sorry)

And also the computer that im joining shows up in the computers container
but is disabled and it doesnt seem to be joined at the client side(no domain
list at logon screen.

Thanks again
Gareth
  #6  
Old February 14th 09, 08:11 PM posted to microsoft.public.windowsxp.network_web
Robert L. \(MS-MVP\)[_384_]
external usenet poster
 
Posts: 1
Default domain problem.

any errors if running nslookup?

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"Gazza" wrote in message
...
Thanks for the reply robert ill have to check that out on monday.

The other thing i forgot to put in the first post was the error message i
get if i try to add a client to the domain.

The Server cannot carry out the request(Something along those lines am not
at work now to check it sorry)

And also the computer that im joining shows up in the computers container
but is disabled and it doesnt seem to be joined at the client side(no
domain
list at logon screen.

Thanks again
Gareth


  #7  
Old February 14th 09, 08:11 PM posted to microsoft.public.windowsxp.network_web
Robert L. \(MS-MVP\)[_454_]
external usenet poster
 
Posts: 1
Default domain problem.

any errors if running nslookup?

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"Gazza" wrote in message
...
Thanks for the reply robert ill have to check that out on monday.

The other thing i forgot to put in the first post was the error message i
get if i try to add a client to the domain.

The Server cannot carry out the request(Something along those lines am not
at work now to check it sorry)

And also the computer that im joining shows up in the computers container
but is disabled and it doesnt seem to be joined at the client side(no
domain
list at logon screen.

Thanks again
Gareth


  #8  
Old February 15th 09, 04:52 PM posted to microsoft.public.windowsxp.network_web
Lanwench [MVP - Exchange]
external usenet poster
 
Posts: 1,547
Default domain problem.

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.


  #9  
Old February 15th 09, 04:52 PM posted to microsoft.public.windowsxp.network_web
Lanwench [MVP - Exchange]
external usenet poster
 
Posts: 1,547
Default domain problem.

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.


  #10  
Old February 15th 09, 05:25 PM posted to microsoft.public.windowsxp.network_web
Gazza
external usenet poster
 
Posts: 23
Default domain problem.

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.



  #11  
Old February 15th 09, 05:25 PM posted to microsoft.public.windowsxp.network_web
Gazza
external usenet poster
 
Posts: 23
Default domain problem.

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.



  #12  
Old February 15th 09, 05:40 PM posted to microsoft.public.windowsxp.network_web
Lanwench [MVP - Exchange]
external usenet poster
 
Posts: 1,547
Default domain problem.

Gazza wrote:
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.


Good. And there are no additional DNS servers listed?

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.


Do try the ipconfig /all. Something is amiss. Could be the DNS suffix.

You could also try running dcdiag & dnsdiag ..


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.




  #13  
Old February 15th 09, 05:40 PM posted to microsoft.public.windowsxp.network_web
Lanwench [MVP - Exchange]
external usenet poster
 
Posts: 1,547
Default domain problem.

Gazza wrote:
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.


Good. And there are no additional DNS servers listed?

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.


Do try the ipconfig /all. Something is amiss. Could be the DNS suffix.

You could also try running dcdiag & dnsdiag ..


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.




  #14  
Old February 16th 09, 09:29 AM posted to microsoft.public.windowsxp.network_web
Gazza
external usenet poster
 
Posts: 23
Default domain problem.

Heres the ipconfig from the server

Windows IP Configuration

Host Name . . . . . . . . . . . . : server01
Primary Dns Suffix . . . . . . . : stc-plumbing.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : stc-plumbing.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC373i Multifunction Gigabit
Server Ad
apter
Physical Address. . . . . . . . . : 00-1B-78-31-5D-0A
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.149
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.149

And hers the one from a workstation

Windows IP Configuration

Host Name . . . . . . . . . . . . : Workstation06
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connecti
on
Physical Address. . . . . . . . . : 00-13-20-9E-FE-D2
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.37
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.149
192.168.0.1
Lease Obtained. . . . . . . . . . : 16 February 2009 07:31:41
Lease Expires . . . . . . . . . . : 19 February 2009 07:31:41

The second IP address listed as a dns server was a test to see if i can
access the internet which worked.





  #15  
Old February 16th 09, 09:29 AM posted to microsoft.public.windowsxp.network_web
Gazza
external usenet poster
 
Posts: 23
Default domain problem.

Heres the ipconfig from the server

Windows IP Configuration

Host Name . . . . . . . . . . . . : server01
Primary Dns Suffix . . . . . . . : stc-plumbing.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : stc-plumbing.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC373i Multifunction Gigabit
Server Ad
apter
Physical Address. . . . . . . . . : 00-1B-78-31-5D-0A
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.149
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.149

And hers the one from a workstation

Windows IP Configuration

Host Name . . . . . . . . . . . . : Workstation06
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connecti
on
Physical Address. . . . . . . . . : 00-13-20-9E-FE-D2
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.37
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.149
192.168.0.1
Lease Obtained. . . . . . . . . . : 16 February 2009 07:31:41
Lease Expires . . . . . . . . . . : 19 February 2009 07:31:41

The second IP address listed as a dns server was a test to see if i can
access the internet which worked.





 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off






All times are GMT +1. The time now is 08:42 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.