You are not logged in.
Pages: 1
Hello,
We're trying to implement a REST server using the TSQLDBServerHttpApi instance. That works in general, but we have a problem connecting to our server from some client PCs. The client application, which we run on these PCs, just returns the "timeout connecting to the server" error. The server is running on the port 80 and we also have an IIS instance running on the same port. The "problem clients" can access the IIS on the server (i.e. show the start page), but can't connect to the REST server on the same port. Does anybody have an idea, what could cause this problem?
Thanks in advance.
Offline
This is an URI registration problem, at http.sys level.
You have to explicitly register each URI for the port 80.
See https://synopse.info/files/html/Synopse … #TITLE_274
and https://msdn.microsoft.com/en-us/librar … p/cc307236
Offline
Hello Arnaud,
Thank you for the quick answer. It seems that we have another problem. When I checked the server using netsh http show urlacl, it displayed the right record for the database URL.
Reserved URL : http://+:80/syndbremote/
User: \Everyone
Listen: Yes
Delegate: Yes
SDDL: D:(A;;GA;;;WD)
For now we're using your HTTP server from the SynDBExplorer (12) sample, which does it automatically. Also the problem can only be observed on some client PCs. Some other clients work fine.
I've given you the wrong error description in the first post. The actual error is winhttp.dll error 12029 "A connection with the server could not be established".
Offline
Hello Arnaud,
It appears to be a client issue. Not really an issue, but the group policy, which disables internet access for any application except of the browser. It's a customers PC, so we just didn't have enough information on this.
Thanks for your help.
Offline
Pages: 1