Re: Problem Loging on to Doman
- From: Superfly Merlin <SuperflyMerlin@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 11 Jan 2006 07:51:03 -0800
If there is a wireless connection you might want to disable it to alleviate
any weird connectivity issues. Log in over hardwire with your account and
check IP info...make sure it's right for the domain. If this was a DNS
problem the admin probably wouldn't be able to log in as himself unless he's
mistaken and had cached his credentials prior to making some network change.
Admin: Log in with your account and make sure you can hit ports 88, 445 and
389 on the DC(off the top of my head, these ports are respectively: Kerberos,
MS DNS and LDAP...not sure if those are the ports needed for login but might
be a good place to start) use telnet:
example (run from cmd): telnet <server ip> <port> (telnet 192.168.1.1 80)
....if it says "could not connect" you are not getting connectivity on the
port...check firewall. A blank window would indicate connectivity...try it
on your webserver by using port 80 if you need to see how things should look.
A general networking problem somehow related to the user account could
cause problems that look like DNS because he's not getting proper
connectivity to the DC. That said I've never seen that particular behavior.
What I have seen, for example, is an inability to load a server-based user
profile due to the firewall not having file and printer sharing allowed - but
that's obviously different because the user account could at least log in.
If you are running any third-party network related apps such as a Cisco VPN,
antivirus with firewall or some other firewall - you may want to log in as
yourself and stop the related services for those apps or stop the Windows
Firewall before trying again. Does the user have admin on the machine? Does
your account? Is one of these things not like the other? If you have a VPN
(PPTP) server available you could create/share a vpn connectoid and then at
the login prompt check the box for "log on using dial up networking" and see
if initiating a VPN connection in your domain allows that user account to be
able to get the required connectivity to the domain.
"Miha Pihler [MVP]" wrote:
> Hi,
>
> How is DNS set up on this client? Where does it point to for DNS servers?
>
> Are there any errors on the client in event logs (Application and System
> Even log)
>
> --
> Mike
> Microsoft MVP - Windows Security
>
> "Neil" <Neil@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:727DBC98-2526-4701-BF64-6E53AC951BB5@xxxxxxxxxxxxxxxx
> > Hi,
> >
> > I am getting the message 'The system cannot log you on now becaouse the
> > domain <DOMAIN> is not available.
> >
> > This s for a user I have set up this morning. I can go to other PC's and
> > log
> > him on fine with no problem.
> >
> > Back to his machine I am unable to log him on. So I try to use my user
> > account, and it logs on to the domain fine, even though I had not used my
> > personal user account on this machine before. I am also able to connect to
> > all the shared resources of the server.
> >
> > I then try the Administrator logon, again fine and all resources for the
> > domain are fine.
> >
> > I then try the user again, and the error appears. It is specific to this
> > user, even though this same user is able to logon using different machines
> > in
> > other offices.
> >
> > Has anyone come across this before? If you have any ideas, I would
> > appreciate them.
> >
> > Thanks in advance,
> >
> > Neil
> >
> > Systems Config.
> > Server:
> > Dual Processor
> > 2GB RAM
> > Windows 2000 Server.
> > Desktop:
> > Dell Laptop.
> > Windows XP SP2
> >
> >
>
>
>
.
- References:
- Re: Problem Loging on to Doman
- From: Miha Pihler [MVP]
- Re: Problem Loging on to Doman
- Prev by Date: Re: best exchange secured option
- Next by Date: Re: msn messenger
- Previous by thread: Re: Problem Loging on to Doman
- Next by thread: Re: Problem Loging on to Doman
- Index(es):
Relevant Pages
|
