domain unavaliable

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

After uninstalling pc anywhere from my win2000 AD , non of my pcs on the lan
are able to logon to the domain. I can go online from any client and I can
browse resource on the server if I login locally to any of the clients on the
LAN.
Restart DNS and net logon to no avail . Any suggestions!
 
AS far as pcanywhere it was pre install by another Tech. Can you shed more
lights on the default policies. What exactly I should be looking for to
resolve this issue? Thanks
 
Cary Shultz said:
I would wonder why you would install pCAnywhere on a Domain
Controller....If it is due to 'remote access' then I might consider the
Terminal Server in Remote Admin mode....

Anyway, have you considered looking at the two default policies...
Click to expand...

Cary, I just found out this post was multi-posted. I replied to the one in
the win2000.dns group, but not sure if posted elsewhere.

My first thought is that I believe it may be a DNS misconfig, otherwise,
good point about the policies. Maybe if a higher security inf policy was
applied to the Default DC Policy ca cause this too. Maybe IPSec in a policy
too?

Question to the poster, Kwise: Curious, what Event log errors, if any, exist
or what else was performed on the machine recently? It could have been
something else prior to that and the system wasn't rebooted until PC
Anywhere was uninstalled. It could also be a hardware issue (bad NIC?). It
could be many things. It could also be Zone Alarm.

Without knowing anything about your system Kwise, it's totally guesswork at
this point and can be caused by numerous issues.

btw Kwise, it would have been to your benefit to have cross-posted to
appropriate groups instead of multiposted so any and all respones will
populate all your threads in all the groups simultaneously.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

If this post is viewed at a non-Microsoft community website, and you were to
respond to it through that community's website, I may not see your reply
unless that website posts replies back to the original Microsoft forum.
Therefore, please direct all replies ONLY to the Microsoft public newsgroup
this thread originated in so all can benefit or ensure the web community
posts it back to the original forum.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services
Microsot Certified Trainer
Infinite Diversities in Infinite Combinations.
=================================
 
Thanks for your heads up
I was not sure how the system works. What this issue that I have , I didn't
which Cat. it falls in. I apologize for any inconvenience.
 
kwise said:
Thanks for your heads up
I was not sure how the system works. What this issue that I have , I
didn't
which Cat. it falls in. I apologize for any inconvenience.
Click to expand...

No inconvenience, it's just were doubling up efforts.

Anyway, did the things I mentioned or Cary mentioned helpful in determining
the problems?

As I mentioned in the other thread in the win2000.dns group:
It would be very helpful to know more about your system, otherwise, it's
really totally guesswork at this time on our part. Put yourself in our
shoes. Wouldn't you need more info to help out?

Ace
 
Ace,

The DNS setting on both DC and client looks correct. Clients point
to the Dc for DNS and DC point to its self. I can ping by name and ip. No
ip-sec policy has been imposed . What do I need to look in the default policy
to resolve this issue?

Thanks
 
In
kwise said:
Ace,

The DNS setting on both DC and client looks correct. Clients
point
to the Dc for DNS and DC point to its self. I can ping by name and
ip. No ip-sec policy has been imposed . What do I need to look in the
default policy to resolve this issue?

Thanks
Click to expand...

If it is anything in the policy, it can be a number of things. But first, it
may be helpful if you can provide the list of data below.

1. ipconfig /all from a client and from your DC(s)
2. The DNS domain name of AD (found in ADUC)
3. The zonename in your Forward Lookup Zones in DNS
4. If updates are set to allow under zone properties
5. If this machine has more than one NIC
6. Do you have a firewall? If so, what brand?
7. Is/are forwarder(s) configured?
8. Do the SRV records exist under your zone name?
9. Event viewer error Event ID#s and source.

Also, run and post the results of these commands please:

netdiag /v /txt > c:\netdiag.txt
dcdiag /v /fix > c:\dcdiag.txt

Also, I had a similar issue with a client the other day. Intermitten issues.
Found it was a bad NIC. Never know, piece of hardware can be causing it too.

Ace
 
Back
Top