• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 478
  • Last Modified:

unable to login to the application server.

hi,

in my office we are using windows server 2003 domain. in this domain, we have one application server which is installed in windows xp machine. till yesterday i am able to login to the machine. from today morning i am unable to log in to that server with any of the domain user. only i am able to log in to the server as a local administrator. i didn't change anything and i didn't update any latest patches.

when i try to log in to the system i am getting the error message:
"windows can not connect to the domain, either because the domain controller is down or otherwise unavailable , or because your computer account was not found. please try again later. if this message continuously to appear contact your system administrator."

i try to ping from server its giving reply. i ping from the xp machine to server then also i am getting replies. i am able to log in though that accounts from other systems i am able to log in.

please help me.
0
ramachandraraju
Asked:
ramachandraraju
  • 6
  • 5
2 Solutions
 
nipponsoulCommented:
Is NETBIOS ping (ping dcname) and FQDN ping (ping dcname.domain.com) reply ok?

Did you check the network settings on the NIC?

Obviously it cannot contact the domain server(s). Check your DNS settings on network properties as well :)

And ... as obvious as it sounds .... check the network cable  and whether the network cars is working ok. If you have bridged NICs check the configuration as well.
0
 
ramachandrarajuAuthor Commented:
i got reply from NETBIOS ping and FQDN ping.
i checked all the network settings. everything is normal.
i removed the old lan cables and try with new lan cables.

but still the same problem.


please help me.
0
 
nipponsoulCommented:
Is the Computer Name of that server located in your Active Directory?

I would try rejoining it to the domain.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
ramachandrarajuAuthor Commented:
i didnt give one important information.

i started one system yesterday, which having the same name in the domain ( previously its the application server). i got duplicate name warning message and stopped the system.

i searched for solution and some are advising that, i should dis join the server and delete the DNS record from the domain and then again i have to join into the domain. this will solve my issue.

please guide me if i do this will i get any issue with my application. because i am using a mail agent application in that server.


help me
0
 
nipponsoulCommented:

Well that's the cause problem then^^

1. First disjoin the actual server which has the application from the domain from the machine itself.

   Just log in to the application server as the local administrator, right click on My Computer, select     properties.
   On the computer name tab, select, Network ID and make the machine a member of a Workgroup. themn restart the machine.

2. Go on your domain controller and first RESET the cpmputer object and then delete it.

3. Go into DNS and delete any entries of that server name in the DNS lists.

4. Allow time for replication if you have more than one DC

5. Re-join that server on the domain.

0
 
nipponsoulCommented:
Also.. after you clear the record in DNS:

Run "ipconfig /flushdns" command on the application server
Restart Net Logon service

Run ipconfig /registerdns after you rejoin the server on the domain.
0
 
ramachandrarajuAuthor Commented:
if do like that will i get any issues with my mail client? and other applications ?

please guide me.
0
 
ramachandrarajuAuthor Commented:
we installed mail agent in this  system  to get mails to entire office.
0
 
nipponsoulCommented:
This is just rejoining a machine ... doubt it would cause problems ... the machine will have the same IP  and the same Computer name NETBIOS and FQDN ... provided the network card TCP/IP settings are the same and the IP is static).

What is your email client ???
0
 
ramachandrarajuAuthor Commented:
mdeamon email agent
0
 
nipponsoulCommented:
I don't see any problem since the machine will have the same name and IP.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 6
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now