NT4 Server refresh Network Neighborhood

I wish to be able to display the current computers on to an NT 4.0 Server SP 6b.

I notice that when a computer logs off the network i.e. the computer terminal is shut down, Network Neighborhood on the server does not update - the logged off terminal is still listed.
The same applies if using NET VIEW.

Eventually the computer is removed from the list. I have not been able to determine how long this takes to occur, but it is certainly longer than 1 hour.

It also seems that there is a considerable time delay between a computer logging on to the server and the information being available to Network Neighborhood and NET VIEW.

Does anyone know if there a way to force a refresh so that the computer list is truly current?

GeoffG

 

Domain or workgroup?

 

Newt

It is a domain.

GeoffG

 

Thanks. I had what I thought was a bright idea but it turned out not to work. Thought doing a SAM Synch from the PDC would do the deed but just tried it and no luck.

This might be a good one to post to http://support.microsoft.com/newsgroups/ and the non-developers section.

 

Thanks Newt.

I will do as you suggest and report back to this board.

GeoffG

 

This looks like a problem with the Master Browser. Generally the PDC or BDC on your subnet. It keeps track of all nodes on the network via broadcast, and after 45 minutes to 1 hour 30 minutes it has refreshed the listings. (that's generally how long a network election takes). My suggestion may be a WINS server. You generally only need this option when using multiple subnets and need NetBIOS name resolution. However when used, all systems register and deregister themselves to it. You can then query the WINS database to find out who's logged on the network.

 

Hi Eric

Thanks for taking the time to respond.

You said" "¦â€¦â€¦ and after 45 minutes to 1 hour 30 minutes it has refreshed the listings. (that's generally how long a network election takes).â€

I take this to mean that the list of connected nodes will not be updated for at least 30 minutes?

If this is so, then my query is probably answered. Perhaps if I say just what I am attempting to achieve you (or Newt, or anyone else for that matter) may be able to assist further. Perhaps you may have other ideas.

There is a domain network consisting of 10 Windows 98 terminals connected via a hub to an NT 4.0 Server. The terminals are housed in individual offices in the building.

At the end of the day a manual backup is performed at the server. The backup operator needs to know that all terminals have been shut down and the accounting package exited before the backup is begun; so each terminal is polled using "˜sneakernet’ i.e. the operator walks to each terminal and ensures that it is shut down.

If the status of each terminal could be displayed at the server as part of the backup procedure, this would save the operator walking around to each terminal. If any were still connected, the operator would know which ones were on and be able to take the appropriate action.

As the backup is carried out soon after the offices are vacated, the update to the list of connected nodes need to occur quickly "“ say within 5 minutes. Might there be a way for the operator to force the server to poll the connections?

GeoffG

 

WhoseAlive.bat

Ping computerA > c:\whosealive.txt

Ping computerB >> c:\whosealive.txt

Ping computerC .......

etc. until you've included all the PCs.

First line has a single > to send the results to a file.

Remaining lines have a double >> to append to the file.

Couple minutes and you can look at the text file to see whose alive and whose not. Run the bat file from the scheduler service on the server and it can be waiting for whomever.

 

Thanks Newt

I had considered that, but had not got beyond considering it.
I would need to shell out of the backup software, test for connections and then present the results to the operator.

I will come back shortly when I have made it work.

 

For the "ping" part, no need to run that from the server at all. Or you could and pipe it to a printer rather than file. Should work fine even with the backup piece loaded and taking focus.

I think there is remote kill available for 9X PCs but haven't looked around lately. For one thing, couldn't tell from your post if a live PC would be a user who left and forgot to shut down or a scientist working frantically on a project. Might be a PC you didn't want to just force shutdown on.

But any alternative to sneaker net is a good alternative IMO.