Unindentified Network

I am running a server machine with Windows server 2008 R2 Enterprise with the domain Constellation.com. It has two wired adaptors, one for cable internet and one for DSL internet. However I have based my network on the cable NIC as cable is more easy to configure. My NIC configuration on the server machine is as folls:-
IP Address                 192.168.0.50
Subnet mask              255.255.255.0
Default gateway          192.168.0.1
Preferred DNS Server  192.168.0.50
The cable NIC then shows as Constellation.com and even the DSL NIC which I Ihave kept as DHCP also becomes Constellation.com
On the workstation Jupiter I recently upgraded my motherboard to P8Z68 Deluxe and that necessiated a new Windows Seven. However I kept the old name of the workstation as Jupiter.
Jupiter workstation Cable NIC configuration is as :-
IP Address                 192.168.0.53
Subnet mask              255.255.255.0
Default gateway          192.168.0.1
Preferred DNS Server  192.168.0.50
Previously with the old motherboard it used to go with this setting to Constellation.com but it does not now it becomes an unindentified network. I changed the Cat 6 cable for the cable internet from the internal PCIe Card to a external NIC Card  DLink DGE-528T but still it shows an unindentified network. However when I change configuration settings to DHCP the NIC Card is identified and starts connecting to the internet. But obviously I want the server configuration.
There is another workstation Emperor on which the cable NIC has the server settings i.e.
IP Address                 192.168.0.51
Subnet mask              255.255.255.0
Default gateway          192.168.0.1
Preferred DNS Server  192.168.0.50
With these settings the cable NIC Card on this workstation  turns into Constellation.com and even the other NIC Card on the DSL network becomes Constellation.com. With the server settings or manual settings the NIC Card is not visible on the router DLink Dir-825 but with dynamic i.e. DHCP it is so. Why is this so.
Why has my network on one workstation has become unindentified whereas on thje other workstation it has not? Is it because that the server machine may have the old configuration of the Jupiter Workstation?
SALEM586Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

SALEM586Author Commented:
I went to the Server Computer named Stellar went into the Active Directory Domains and Trusts and deleted the workstation computer Jupiter and the Home Computer. Then I tried to add back Jupiter Computer  into the Domain'Constellation.com' but now I cannot. What did I do wrong? I thought that the computer named Jupiter with the old motherboard was creating problems but it was not so.
0
lisfolksCommented:
If I understand correctly, your problem is with the Jupiter workstation. You replaced the motherboard and installed Windows 7. Then you manually set the IP configuration to the following settings:

IP Address                 192.168.0.53
Subnet mask              255.255.255.0
Default gateway          192.168.0.1
Preferred DNS Server  192.168.0.50

However, that did not work, so you turned on DHCP in Jupiter's IP configuration - and it works. But returning to the manual configuration, it doesn't.

Did I get that right?

If so, then I will ask: when you turn on the DHCP, what IP Address, Subnet Mask, etc, appear in Jupiter's configuration?

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
SALEM586Author Commented:
Thanks to listfolks I went to command prompt and opened up ipconfig and soon realized that both the cat 6 cables for the Cable NIC and the DSL NIC were connected to the same switch. This was probably because the cat 6 cables were the same Belkin manufactured green cables and I could not distinguish them from each other. So I put a label on one of them as to not make the same mistake again. Obviously with the change in the motherboard I had to take the cat cables off and put them back on the new motherboard. Unidentified network became recognisable and the particular workstation was able to join the domain again.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Legacy OS

From novice to tech pro — start learning today.