SALEM586
asked on
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?
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?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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.
ASKER