HELP. how to run a PC on two networks

[CyBOrz PaCe]

Ok. I'll try to make this as brief and clear as possible.

I have a PC at work on our company's domain. It is running win XP pro. It has dual NIC's in it.

I also built a server rack and wanted to create a seperate internal network for my office. The server was set up as a file server in a workgroup.

Our office area is cabled for just that. We have two jacks on the plates on our walls. One for the company domain and one wired by itself for us to use internally.

Here is the situation. Our PC's are in the company domain. Our internal network and server is in a workgroup. Our PC's are cabled to both. If I enable the domain connection I can access the company domain w/no problem. But when I disable the domain connection and enable the internal workgroup connection. I cannot see the workgroup.

I know this is because I am not in the work group. So I attempted to take the PC out of the domain in into our workgroup. It worked. I could access the server and my share and backup my data to the server.

But then when I tried to move my PC back into the domain I received an access denied message. After several attempts, I called our network support and was informed that when you move a computer out of the domain in our network you corrupt the computer account in active directory. I don't believe that is normal and sounds to me like a problem with our company's network. But never the less, it is the way it is in our domain.

So my question is, how can I have my PC hooked up to both my company's domain and my internal network and be able to switch between the two with the least amount of headache?? Do I need to make my internal network server a domain controller?

I just had another thought. What about making my internal network a domain controller and name the domain the same as the company's domain? Using non-routable IP addresses? Neither domain would know the other exists. Of course my PC would know there are two domains named the same thing... would that cause a problem.

Man, I'm in over my head in this one. If anyone has any ideas or wants to help but needs more info please let me know.

Thanks a bunch!

 

[CyBOrz PaCe]

^^ anyone?

 

[Rhi]

This might be what you're looking for.

-Rhi

 

[CyBOrz PaCe]

Thanks Rhi.

That does look like one solution.

I did promote the member server on my internal network to a domain controller and name my internal network domain the same as my company's domain. That way when anyone is signed into their PC they are in the correct domain no matter which network they are on.

Since the internal and external don't ever see each other and the internal IP's are non-routable ( 192.168.0.1 etc ). I am hoping their won't be a problem.

I tried my PC and could see the server over the internal network and it could see my PC. But when I tried to access it I couldn't. I am not sure whether I just need to set up my account or what. I did create an account in active directory for my PC but the server's event viewer says there is a "trust relationship" problem and references the SID.

I am now wondering whether that is a problem I can overcome or if the SID will stop me from running on the 2 networks.....

I had to stop for today. I'll try more tomorrow.

CyBOrz PaCe