Server 5 on W2000 doesn't show locally

[simonkay]

Hi,

we're using server 5 on a W2000 server with about a dozen files served to 25 users in a standard Windows domain. We've been running it a couple of months with no problems. Access from a 5.5 client is as usual through the File/Open Remote/Hosts dialogue, and the server was up until now always visible as a local host when in the same domain (subnet).

Yesterday the server was no longer listed as a local host. I am able however to connect using the "Specify server" option, and directly typing the IP address.

I can furthermore make the server become visible again as a local host by restarting the service on the server; but after doing this twice it again disappears after an hour or two.

Any ideas?

Thanks in advance

Simon

[Anatoli]

Did someone updated the Windows recently?

[simonkay]

Don't think so, server is stable since FM installation several months ago. However, a few hows prior to this problem appearing I added two files to the server. These files (well, one, because one is multi user hidden) appear in the local list no problem (until thelocal list disappears altogether).

FWIW, the server runs W2000 5.00.2195 SP2. FM Server is v 5.5 (sorry, not 5 as I stated above), and the clients are mostly 5.5v2 (N) with one or two v1 (according to the application service log).

I'm not able to identify yet if the disaapearance of the local list is related to a client trying to connect, or if it is a server software problem (OS or FM). I cannot find any logged events that would appear to trigger this or coincide.

Again, it is possible to connect specify the IP address of the host/server.

Simon

[esteshk]

I have fought this issue for some time and have now "abandoned" the Host window as a method for accessing may solutions. I now use Opener files exclusively that address my files directly via the IP#. In my environment, I believe the problem is caused when the network infrastructure fails to "carry" the FileMaker Server broadcast signal. We have run many tests using different combinations of hardware (network) and the problem persists. On a positive note, I believe the use of opener files enhances the user interface/experience and make my solutions look and feel more professional.

[simonkay]

Thanks, good idea indeed I used to use this approach before I used server (smaller workgroups). I just migrated my users to using the Hosts button... but I think indeed using opener files is clearer for the average user.

Also allows them to put shortcuts (to the opener file) on their desktops, which is what they really want.

Meanwhile, we are going (for for other reasons) to move the server application onto another W2000 server, so we'll see if anything changes.

Simon

[jmkimmel]

We have Server 5.5 running on Win 2000 also and it comes and goes as far as being able to see it in the hosts window as well. I think it is a Windows issue because if we restart the server, the Hosts window is populated again. It has not been a major issue for us, just inconvenient.

Just thought I'd let ya know it probably isn't just your machine...