We have a group of users in one of our remote offices who are running Windows 95 on Ethernet who are unable to net use the primary virtual server in one of our Vinca clusters.<br>
<br>
Config: Primary - Compaq Prosignia 500 <br>
& NT Server 4.0 (SP4)<br>
Secondary Vinca 4.2<br>
<br>
Workstations: Can ping & tracert every Server, Router, & Switch on network (including problem server).<br>
Can net use all other Servers & workstations except that problem server -- can only net use the Physical Server (Z).<br>
Changed to Static & DHCP settings (no difference).<br>
Changed to different routers.<br>
<br>
Other PC's and workstations outside of that group don't have that particular problem -- both 95 & NT workstations can net use the Logical (Vinca) & Physical (Z)server.<br>
<br>
<br>
We noticed that when we failed over the server to is co-stanby we were not able to ping the server anymore. We failed back and then were once again successful in pinging it. We had no problems pinging the physical server (Z server) during all of these tests.<br>
<br>
Any clues?
<br>
Config: Primary - Compaq Prosignia 500 <br>
& NT Server 4.0 (SP4)<br>
Secondary Vinca 4.2<br>
<br>
Workstations: Can ping & tracert every Server, Router, & Switch on network (including problem server).<br>
Can net use all other Servers & workstations except that problem server -- can only net use the Physical Server (Z).<br>
Changed to Static & DHCP settings (no difference).<br>
Changed to different routers.<br>
<br>
Other PC's and workstations outside of that group don't have that particular problem -- both 95 & NT workstations can net use the Logical (Vinca) & Physical (Z)server.<br>
<br>
<br>
We noticed that when we failed over the server to is co-stanby we were not able to ping the server anymore. We failed back and then were once again successful in pinging it. We had no problems pinging the physical server (Z server) during all of these tests.<br>
<br>
Any clues?
