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

NT 4 & 2000 lose profile on server

I am running NT 4 and 2000 dual boot.
The problem is that that when ever I swith form one OS to another I have to go into the network settings and reset the connectin with the server, or else it cannot find my profile to log me in. I think it has to do with the SID's ,but I am not sure how to synchronize them.  What can I do?
0
e_P
Asked:
e_P
  • 3
  • 2
  • 2
  • +2
1 Solution
 
White_BuffaloCommented:
I'm not sure, but I would guess that NT4 and Win2K store profile info differently.

How are you getting into network settings to reset the connection with the server if you are not logged in?
0
 
t_ogawaCommented:
(1)is it roaming profile?
(2)NT4 and 2000 have same computer name ?

0
 
t_ogawaCommented:
(1)is it roaming profile?
(2)NT4 and 2000 have same computer name ?

0
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
e_PAuthor Commented:
It is not a roaming profile.
Yes they do have the same computer name, sorry should have mentioned this.

to change the network settings I go into the Network properties. Take the machine out of the domain and then put it back in.
0
 
jdtanCommented:
Yeah, I have the same problem. It's not losing your profile. It's just a conflicting computer name. You could change one computer name, but you would then (presumably) lose DNS ability for it.

What I do is just have one OS not be in the domain. I still have full IP connectivity, and I can still map shares with any server in the domain.
0
 
e_PAuthor Commented:
For testing purposes I need to have both of the OS's able to be part of the domain.  I think I am going to try to have 2 computer names for each OS. I'll see what happens.

-P
0
 
jdtanCommented:
I think that should work fine. Again, the only problem is that you can't do reverse DNS on it, but if you ever need it, you could always use the direct IP instead.
0
 
ioloCommented:
Had this ***same*** problem.  Here's the fix:

In the OS that was last installed, go into the network identification properties (right-click on network neighborhood or the W2k equivalent) and change from a domain to a workgroup (or vice versa).  Reboot.  Go back into the network identification properties and set yourself back up for the domain/workgroup.  Under W2k this should immediately allow you to connect back, and then when you reboot to the NT4, you should be ok as well (providing you have not totally confused the server with previous attempts to fix this like I had).  If this doesn't work, I'd try doing the same procedure to the second OS (try W2k FIRST though).

This has worked for us five times in the last two weeks.
0
 
e_PAuthor Commented:
iolo:

I have been doing this for a while now.  That is the only way I can get the machine to log back on into the domain.  Once I reboot and then go to NT 4 I have to do the same to it.  If I go back to Win2k, once again, I have to do the same thing over again.
0
 
ioloCommented:
Couple of ideas:

1.  You need to have each "OS" with a separate "computer" name on the server.

2.  Is this using user-accounts or an admin login.  If user accounts, you should set each OS up as a separate login.  I think the server wants to verify that you are indeed who you are and if it's coming from a different OS, it thinks something is wrong.

If these two things don't help, you most likely have to do the re-installation of one or both OS's and set them up this way from the beginning -- as you may be too far gone at this point for hope of a "fix".
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

  • 3
  • 2
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now