Re: Removed from domain and unable to logon

Thanks. I already tried uninstalling McAfee on the laptop. It didn't help.
The only active firewall is my router. Windows Firewall and McAfees are both
disabled.

Tried using it on an ethernet cord instead of just wireless but still no luck.

--Gabrielle



"JS" wrote:

My guess is (having been an Admin for NT 4) is that McAfee is the problem,
which you probably already know by now. I say this because a number of
software packages which ran fine on a local desktop did not run or were not
supported on NT.

You may also want to check the firewall settings in this product as they may
be getting in the way.

JS

"Gabinka" <Gabinka@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0A27AFC6-E3A0-4885-B255-31E6804B31C5@xxxxxxxxxxxxxxxx
I have a similar problem. For some reason, at some time, 2 of my computers
(both XP Pro, both wireless) failed trusting my domain (NT 4.0 sp6) which
they had been on for years. I had recently installed McAfee VirusScan
Plus
2007 on one of them (which also housed my web server which stopped serving
right about then).

A few days ago, I tried to set up a share on the webserver. I was asked
for
domain admin credentials, which I gave. I was told the password was wrong.
It
wasn't. I tried several, all domain admins, all of which can log into
other
computers.

Yesterday, I tried to get to an existing share on that server and was told
I
didn't have permissions. I checked the share and noted that all my domain
accounts were not in it anymore. My share permissions had actually been
changed.

Today, I went to compare that to what was going on on my XP laptop, which
has had McAfee for a year now. And voila, the same problem. Domain
permissions were gone from the shares and I couldn't add them.

So I go to my NT server box and check Server Manager. I'm told for both of
those computers that "The trust relationship between this workstation and
the
primary domain has failed."

I uninstalled McAfee. After much finagling (removing it from the domain,
adding it to a workgroup, and adding it back to the domain, rebooting
between
each), I finally got the webserver back on. I had actually tried changing
its name, to which it replied that it was it's original name and put it
back
on the domain.

I tried the same with the laptop. To no avail. I've removed it from
Server
Manager. (It never actually leaves the list.) I've set it to workgroup.
I've readded it to the domain, both via Network Identification on the
laptop
and Server Manager on NT. Repeatedly. I've changed it's name. Same
thing:
trust relationship failed. I've tried restoring from a restore point.
The
only one I had was from 4:15 this morning. I tried it. It still won't
trust
the domain to which it belongs.

Any help? (I studied MCSE courses under NT 4 but 1) it's been a long time,
and 2) I only took half the tests before deciding I didn't want to be a
network admin. I am, however, an MCDST. I've been working in tech
support
for 8 years. I'm at a loss at the moment.)

--Gabrielle

"Bruce Chambers" wrote:


By changing the computer from the domain to a workgroup, you
destroyed the trust between the domain and the machine. In doing so,
you've also rendered your domain login credentials as invalid. You'll
need to be physically connected to the domain network, you'll need to
have administrative privileges to the workstation, and you'll need to
have sufficient privileges on the domain. Then you can add the machine
back on to the domain, after having first deleted the computer's old
domain account (unless you've also renamed the computer).

Take the computer to your company's IT department for repairs.


--

Bruce Chambers

Help us help you:
http://dts-l.org/goodpost.htm
http://www.catb.org/~esr/faqs/smart-questions.html

They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. -Benjamin Franklin

Many people would rather die than think; in fact, most do. -Bertrand
Russell




.

Relevant Pages

  • Re: More on Remote Desktop
    ... on your firewall to the world, you will almost certainly get hacked. ... between your clients and server on your own LAN. ... your laptop into that LAN server has got to be making these two public IP's ... PPPoE connection to my ADSL ISP. ...
    (microsoft.public.windowsxp.network_web)
  • Re: 32-bit TCP/IP Connection
    ... the firewall which I have NEVER had to do. ... webistes as that ability is shut off at the host server. ... I am on a paid up subscription service with McAfee and have been for 2 years ... The web server may not have the FrontPage Server Extensions installed. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Win XP Laptop not connecting in RWW
    ... > I've been making the Firewall settings on the laptop. ... > setup on Server since the router has firewall configured. ... >>> I can ping from the laptop to the SBS2003 computer. ...
    (microsoft.public.windows.server.sbs)
  • Re: domain cant access, pathname not found
    ... I did a nslookup on his laptop, ... and entered the ip of the server ...samething pathname not found. ... I turned off his windows firewall, ... Are you using DNS, or NetBIOS name resolution? ...
    (microsoft.public.windowsxp.network_web)
  • Re: More on Remote Desktop
    ... connection as stand alone workstation to access the internet. ... being used as storage of huge files and as a fax server. ... What are you using for a firewall? ... Do you mean that your laptop is making a Dialup ...
    (microsoft.public.windowsxp.network_web)