MBNelsonCR
IS-IT--Management
We have a Win2000 Server (Network is NT4 with two Win2k Stand Alone Servers) named JSE08 with two Nics in it. The 1st Nic was assigned the IP of 90.0.0.8\255.255.255.0 which is for Exchange 5.5. The second Nic was assigned the IP of 90.0.0.58\255.255.255.0 and was to be used for interfacing with a IP based Time Clock (Access Database only, no application).
Everything worked fine but when we started monitoring packet traffic we found that the majority of the traffic was running through the second Nic (Time Clock). Wanting to keep the Time Clock traffic seperate, we then moved the second Nic to a Catalyst 1900 Switch along with the connection from the time clock, thus isolating the two from the rest of the Network.
All but five boxes (out of 67) switched over right away with no problem. Of the five two (Win2K Pro) boxes are affected in the strangest way.
The problem is that one minute they are able to log on to the Exchange Server (Outlook 2000) and the next they cannot. When they can log on and you ping JSE08, you get back the IP 90.0.0.8 (which is the right NIC). When they can't log on and they ping JSE08, you get back the IP 90.0.0.58. One of these boxes was put on the Network [Brand new computer] after the switch was made. It was never on the Network with 90.0.0.58 as a path to the Exchange Server.
We have looked at DNS, tried clearing ARP Caches, checked every Hosts and LMHosts file we can find but to no avail. The change appears to occur randomly, although tomorrow we are going to see if we can time the changes to see if there is a pattern.
So in a nutshell, this change occured because we moved two cables to another switch. We have two boxes that cannot reliably access the Exchange Server. I know we are missing something here, which may be obvious to some of you but not us.
Any help would be appreciated.
Mike
Everything worked fine but when we started monitoring packet traffic we found that the majority of the traffic was running through the second Nic (Time Clock). Wanting to keep the Time Clock traffic seperate, we then moved the second Nic to a Catalyst 1900 Switch along with the connection from the time clock, thus isolating the two from the rest of the Network.
All but five boxes (out of 67) switched over right away with no problem. Of the five two (Win2K Pro) boxes are affected in the strangest way.
The problem is that one minute they are able to log on to the Exchange Server (Outlook 2000) and the next they cannot. When they can log on and you ping JSE08, you get back the IP 90.0.0.8 (which is the right NIC). When they can't log on and they ping JSE08, you get back the IP 90.0.0.58. One of these boxes was put on the Network [Brand new computer] after the switch was made. It was never on the Network with 90.0.0.58 as a path to the Exchange Server.
We have looked at DNS, tried clearing ARP Caches, checked every Hosts and LMHosts file we can find but to no avail. The change appears to occur randomly, although tomorrow we are going to see if we can time the changes to see if there is a pattern.
So in a nutshell, this change occured because we moved two cables to another switch. We have two boxes that cannot reliably access the Exchange Server. I know we are missing something here, which may be obvious to some of you but not us.
Any help would be appreciated.
Mike
