Question : about a RAS connection

Hello

I have many clients connected at my LAN using RAS connection and TCP/IP only, i when a client connect, it appear in my LAN Browser under Win95. When this client close his connection, the machine continues in my Browser.
How to eliminate the problem?
thanks

Answer : about a RAS connection

This is not a bug, it is the way the browser fuctions.  The Browser is not accurate, and not an accurate way to see what's on the network. There is a built-in delay from the time a PC is removed from the network, and the time it is no longer visable in the browse list.  

Here is some stuff from TechNet that may help explain.


------------------------
Browser Failures with Microsoft Networking
A failed server stops announcing itself. When the master browser does not receive a server announcement for three of the server’s current announcement periods, the master browser removes that server from the browse list. It might take up to an additional 15 minutes for the backup browsers to retrieve the updated browse list from the master browser, so it could take as long as 51 minutes from the time a server fails to when it is removed from all browse lists.
Because a backup browser announces itself in the same way as a server, the procedure when a backup browser fails is the same as that for a server. If the name of this backup browser has been given to any clients, attempts made by those clients to contact this backup browser fail. The client then retries the NetServerEnum API call on another backup browser on the client’s list of browsers. If all the backup browsers that a client knows have failed, the client attempts to get a new list of backup browsers from the master browser. If the client is unable to contact the master browser, it forces a browser election. The client then returns an error to the application, indicating that the master browser could not be found.
When a master browser fails, the backup browsers detect the failure within 15 minutes. The first backup browser to detect the failure forces an election to select a new master browser. Between the time the master browser fails and a new master browser is elected, the domain could disappear from the list of domains in the browse list. If a client performs its first NetServerEnum API call after the old master browser has failed but before a backup browser detects the failure, the client forces an election. If a master browser fails and there are no backup browsers, browsing in the workgroup or domain will not work correctly.
When a domain master browser fails, other master browsers see only servers on their same local subnetwork. Eventually, all servers that are not on the local subnetwork are removed from the browse list.
How Servers Announce Themselves in Microsoft Networking
When a server is started (including any computer running File and Printer Sharing for Microsoft Networks), it announces itself by sending a server announcement to the master browser every minute. This announcement uses the special NetBIOS name of workgroup\0x1d. As the computer continues running, the time between server announcements is increased until it eventually becomes once every 12 minutes.
If the master browser has not received a server announcement from a computer for three announcement periods, the computer is removed from the browse list. Therefore, there might be up to a 36-minute delay between the time a server goes down and the time it is removed from the browse list.