"Find server" does not work for one of the services

[former_SQLA_member1694896]

Hello, all I have a development server with several DB services (v16) running on it. There is no problem connecting to any of the servers on this machine via "find server", for the exception of a single service. Question: why would broadcasting differ for different services on the same machine. Below is the extract of the log:

//--------------------------

13:49:36 Attempting to connect using:
UID=dba;PWD=********;ServerName=g4_center_local;CON='SQL Central 8';LOG=c:\\temp\\g4_center.txt;LINKS=TCPIP();ASTART=NO
13:49:36 Attempting to connect to a running server...
13:49:36 Attempting TCPIP connection (no sasrv.ini cached address)
13:49:36 Looking for server with name g4_center_local
13:49:36 Sending broadcast to find server
13:49:36 Using broadcast address of: 20.20.21.255:2638
13:49:36 Using broadcast address of: 127.255.255.255:2638
13:49:36 Using broadcast address of: (ff02::1):2638
13:49:37 Resending
13:49:38 Resending
13:49:39 Resending
13:49:40 Resending
13:49:41     Server not found (no reply received)

//--------------------------

Thank you

Arcady

[Breck_Carter]

Was the server started with -sb=0?

[former_SQLA_member1694896]

No. Must it be?

[Breck_Carter]

Not in your case... if it was set to 0 it might explain your symptom.

[graeme_perrow]

If more than one DB server is running on the same Windows machine, sometimes one of them will not receive UDP broadcasts, which is how dblocate finds servers. This has been a problem on Windows forever and we have never been able to find a solution or even replicate the problem reliably.

[VolkerBarth]

So no -sb=-1 switch aka "Ignore all Windows Broadcast issues"? 🙂

[Former Member]

Have you tried using DBLocate to see what servers (addresses & ports) exist on your network?

-sb=0 means "Ignore all broadcasts", -sb=1 means "Ignore all DBLocate broadcasts"

Starting without -sb anything means machines can find a server more easily.