V
Valdy Valdy
Since we do the updates, we found 1 server after reboot we are not be able to ping the NETBIOS (name) of the server from other devices BUT we could ping the IP Address of the server though ?!?!
We also found that when we go to Network (under Network and Sharing Center) and we could NOT find that server name. We could find any servers/desktops.
This network is pretty simple. It a Workgroup (not a DOMAIN) and the DNS on the device pointing to the router/firewall type device.
WINS are also turned on the server and any other devices.
The reason we need to work due to this server is apart of sync (as a Replica Server) in Hyper-V replication. It required to identity the computer object as a replica server when the replication sets.
It seem related on the network discovery issue. Any ideas?
Isadewa
Continue reading...
We also found that when we go to Network (under Network and Sharing Center) and we could NOT find that server name. We could find any servers/desktops.
This network is pretty simple. It a Workgroup (not a DOMAIN) and the DNS on the device pointing to the router/firewall type device.
WINS are also turned on the server and any other devices.
The reason we need to work due to this server is apart of sync (as a Replica Server) in Hyper-V replication. It required to identity the computer object as a replica server when the replication sets.
It seem related on the network discovery issue. Any ideas?
Isadewa
Continue reading...