Need help on this!
I'm trying to connect and send a message from my client pc to our host server (Windows Server 2012) via TCP/IP. I configured the DTC connections and also opened the firewall but I still get this error.
Any suggestions on what to configure in order to fix this?
UPDATE: Here is the "View Detail" section:
Related
I can't connect to the KDE GUI installed on my Debian server, using NoMachine. Connection over SSH (Both through PuTTy as X forwarding) works just fine, but somehow I can't figure out how to connect using NoMachine and the NX protocol.
I installed the NoMachine server on my Debian server (nomachine_5.1.54_1_amd64.deb), which seems to work fine. It listens on port 4000. I disabled the firewall on the server.
Then I installed NoMachine on my windows system and tried to connect to the server, using the same IP address as with the ssh connection, and the login credentials I use to login on the server.
I approach the server from another network, using a VPN connection and the HTTP proxy for the network connection.
I tried the tips provided online, but can't get it to work. I still get the error message:
Could not connect to the server.
Error is 138: Connection timed out
Help would be highly appreciated!
You should use the same IP address that is shown in the Welcome GUI like the attached image (taken from the nomachine website)
nomachine welcome gui showing where to connect
I am using the "test.udl" to test the connect.
When I use the IP which is from the router, it can connection test is succeeded.
Then I try to use the real IP for testing connect, it got fall.
The router has set as below:
Archer C2>forwarding>Virtual Server:
Service Port=1433,1434,49172
Ip address=192.168.0.100(Permanent)
And I have closed the firewall in windows.
The Sql server configuration manager setting:
TCP IP Properties>IP Address>
IP1:
Active:yes
Enabled:yes
IP Address:119.246.x.x
TCP Dynamic ports:0
TCP port:null(unset)
IP2:
Active:yes
Enabled:yes
IP Address:192.168.0.100
TCP Dynamic ports:0
TCP port:null(unset)
test.udl test information:
Fail test
server name:119.246.x.x\server
Use Windows NT integrated security
result:
Test connection failed because of an error in initializing provider.
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
succeed test
server name:192.168.0.100server
Use Windows NT integrated security
result:
Test connection succeeded.
Does anyone know where i got wrong?
It is a bug.
SYMPTOMS
When you try to connect to a clustered Microsoft SQL Server 2005 or Microsoft SQL Server 2000 named instance by using the "servername\instancename" syntax, you receive the following error message:
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
You may receive this error message when the following conditions are true:
SQL Server 2005 or SQL Server 2000 is installed on a cluster.
You are connecting to a SQL Server named instance by using TCP/IP sockets.
IPSec policy is enabled on the client domain.
IPSec policy is not enabled on the server domain.
CAUSE
This problem occurs during the discovery phase of the connection. The IPSec policy on the client drops packets from the server when the source IP changes.
WORKAROUND
To work around this problem, you have to hardcode the TCP port or the Named Pipe of the SQL Server named instance. To do this, use a connection string that is similar to one of the following:
[oledb]
; Hardcoded TCP OLE DB initstring
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security >Info=False;User ID=clientID;Data Source=tcp:TcpIpAddress,port
[oledb]
; Hardcoded Named Pipes OLE DB initstring
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security >Info=False;User ID=clientID;Data Source=np:\ServerName\pipe\MSSQL$InstanceName\sql\query
*Source taken from https://support.microsoft.com/en-us/kb/888228
Hope it helped
I have solved it. It may cause of the default port is not 1433.
I checked the log file viewer(SQL server Management studio>SQL Server Agent>Error logs>current(archive is also work))
only tick on the sql server check box
find "server is listening on[ 127.0.0.1 xxxx].
In my case it is 9662/9663
I add them all in my router and succeed to connect.
Thank you all above.
Our InstallShield (IS) 2010 client on Win7 and XP are no longer able to communicate to the licensing server.
The IS clients have not connected in a while therefore it is hard to tell when it "broke".
The licensing server is a Win 2008 server running 11.11.0 FLEXNET
Our license is up to date.
The ports are open and I can telnet to the port that the licensing server (port 27000) is running on.
Ran a wireshark trace, we can see the port connection being established on 27000 but then the windows client abruptly terminates the session.
Windows firewall on client and symantec software has been disabled.
The error from the client is “License Error 96 – InstallShield could not acquire a license because you are not entitled to use this software. You can try to reestablish the connection or exit InstallShield”
Thank You for looking.
Solved it. I ran a wireshark trace and found the following :-
IS Client opens connection to InstallShield License Server Configuration port.
IS client then opens up a second connection to a different port on the server used by Vendor Daemon: mvsn.
Solution:
Log onto the admin tool and valid what ports are listening for the License Server Configuration and Vendor Daemon:mvsn. (might be best to lock down the ports in the admin console otherwise they will be dynamic and change if the services are restarted)
Make sure you can telnet to these ports from the IS client.
I am having an issue with FileZilla, when I try access my FTP account, I get this:
Status: Connecting to xxx.xxx.xxx.xxx:xx (Ip adds:port)
Error: Connection timed out
Error: Could not connect to server
Status: Waiting to retry...
Status: Connecting to (Ip adds:port)
Error: Connection timed out
Error: Could not connect to server
This was working fine till yesterday. It works on another pc, but its not working onn my pc now. I tried disabling Windows Firewall (as I am using Windows 8 OS). Also I completely reinstalled FileZilla, still that didn't do it. Is there anything more I can try?
I was connected to the Internet from another Laptop, with sharing the internet connection. So there was the problem, it had restricted to access the ports. When I connected directly to the Internet the problem was solved.
I had a similar issue. Turned out I was using an incorrect protocol to login to the ftp server. The ftp server was ssh secured. Selecting SFTP option instead of FTP worked for me.
https://vincent254.wordpress.com/2015/03/16/what-to-do-incase-you-get-this-filezilla-connection-error/
You might need to write the host in this format
ftp.example.com
This works if you are having the following error as well
ECONNREFUSED - Connection refused by server
Change Your Internet Connection then connect FileZilla
thanks
I have been uploading to Azure for at least six months. From this afternoon onwards I now get messages like this:
There was no endpoint listening at https://management.core.windows.net/xxxxxx/services/hostedservices that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
Unable to connect to the remote server
No connection could be made because the target machine actively refused it 127.0.0.1:8888
Can anyone give me advice on what's wrong. I tried to upload a new management certificate. That worked fine but then said "authentication error".
I have the same problem. It doesn't matter if the Fiddler is ON/OFF or the computer has been restarted - the problem is in Fiddler Option.
The msg was: "Unable to connect to the remote server No connection could be made because the target machine actively refused it 127.0.0.1:8888"
Go=> Fiddler/Tools/Fiddler Option/
Connection Tab:
make sure that "Allow remote computers to connect" is NOT checked
make sure that "Monitor all connections" is NOT checked
Here is a sample video:
http://screencast.com/t/S8y9NbpveSjd
Hope this helps.
Can you please check if Fiddler is running or not? Normally when you run Fiddler it acts as a proxy and listens at port 8888.
Hope this helps.
I have the similar issue. When I use Visual Studio 2013 to download an extension. It can not connect the remote site.
Assi.NET's method doesn't work. Which means unchecked "Allow remote computers to connect" and "Monitor all connections" still can't get rid of the problem.
To fix it, I find in the machine config file, I added something to enable default proxy. Make sure you DISABLE it.
The correct code is:
<system.net>
<defaultProxy
enabled = "false"
useDefaultCredentials = "true">
<proxy autoDetect="false" bypassonlocal="false" proxyaddress="http://127.0.0.1:8888" usesystemdefault="false" />
</defaultProxy>
</system.net>