The server is located in Germany and I am in Africa.
When I was in Germany I can connect to the server (same newtork with the server or via other connection). But in other country I can not connect, after 30 second will fail. I though that's the Config was wrong, but it looks that Timeout issue.
I am usign Windows 10 with OpenVPN GUI, and I have not access to the Server Config side.
Can it be a router issue or what?
I added mssfix 1200, it solves my problem
Related
I've got a problem with IIS. I got a ASP.NET application there running and I am able to connect to it from local network (http://192.168.100.121:12002/) and from outer network too (185.91.165.134:12002 , connecting via phone, because router doesn't support this feature).
The thing is when I try to connect via a domain name queue.laststep.eu, it says error: timed out.
I've asked my friend to tracert this domain name and it finished at the router the server is connected to, so I suppose DNS is configured properly.
Does anyone got an idea what may be blocking inbound traffic? (Firewall is off, ports on our primary router are forwarded...)
I am attaching a screenshot of the site bindings(got to put it on 3rd party server due to low reputation... https://imgur.com/a/hTvqivY)
Thank you for help!
We have oracle oledb connections in SSIS packages that are working well on windows server 2008.
We moved them to windows server 2012 and installed the needed softwares. We installed oracle client (oraoledb driver), moved tnsnames.ora, ldap.ora and sqlnet.ora to %Oracle_Home%\Network\admin path, add %Oracle_Home% and %Oracle_Home%\bin to path variable.
But on server 2012 oracle connections are giving this error ORA-12541: TNS: no listener. Where as on server 2008 same oracle connections are working fine.
Looked so much across internet but found these solutions:
Check tnsnames.ora
Check listener is running
Check path variable contain oracle home, oracle_home\bin
I don't see a problem with tnsnames.ora because same file is present on both window servers. Correct path variables are also set. Listener is also running (since SSIS on server 2008 is connecting). And I am able to ping oracle db server from both machines.
Can anyone suggest anything that we may try.
To put a formal answer in here.
Basic troubleshooting steps with SSIS:
Use the database native tools to check connectivity
In this case for Oracle that is SQLPLUS.EXE
If you have an issue with native tools then it isn't an SSIS issue
Check that you can resolve the host by using PING <hostname>.
If that doesn't work try PING <ip address>
If ping works, check the port with TELNET <host> <port>
If that doesn't work, either the service is not listening or you need to get your network guys to open the port
This goes for any network service
i.e.
SQL Server (default port 1433)
a web server (default port 80 for unencrypted comms)
I have developed a asp.net website and published in a server.Whereas everything works perfectly in that server if i give browser from that IIS manager, and in server ( published system ) everything works perfect.But i need to access the same published application also in the other systems also ( which are connected in same network ). How is it possible..??
NOTE:
1. Used IIS 7.
When tried to connect from another system from same networ getting error as follows
The socket connection to 172.31.7.243 failed.
ErrorCode: 10060.A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 172.31.7.243:90
If Your are accessing Your application on Hosted Server like this then just replace
localhost with ipaddress of hosted server to access it over the network
[localhost]/MyProjectName
then like this:
[IPaddress_of_HostedServer]/MyProjectName
It is possible that the HTTP traffic on port 80 incoming from the local network is blocked.
You should check if ISA server is installed on your server and if so if HTTP traffic on port 80 is allowed or not. If it's blocked try to allow it for the local network ip range.
Edit: Or port 90 as your error code states, but why are you working on port 90?
I have created a SQL VM on Microsoft Azure and it's been like a walk in the park:
I was able to connect via RDP all the time. I installed an app to IIS and it was working ok.
Now, i wanted to connect from the outside world, but Chrome just gives me the page is not available error.
My DNS name is sqlmilos.cloudapp.net.
I took down windows firewall on windows server.
IIS is bound to port 80.
As I understand I connect to my VM via cloud service which was created at the same time as VM, and it has same dns name: sqlmilos.cloudapp.net
That cloud service has 2 input endpoints (shown in dashboard):
SQL : 23.102.171.184:5986
SQL : 23.102.171.184:63907
That 63907 port is for RDP and it's working, obviously.
I thought maybe I should bind IIS to 5986 port, just for test, but iis says that port is already used.
So, I was hoping that somebody could give me some pointers how to resolve this.
Best regards,
UPDATE:
I just realized that you can add you own endpoints to VM, so I added one for port 80, so now I have 3 ports open: 80, 5986 and 63907,
but I still cannot connect to application.
I am unable to connect, for example, via http to a brand new installation of 64-bit Windows Server 2008. The server is on a domain, but is not DC (that's another problem altogether).
The IIS7 is running on the server and the website is accessible locally via http://localhost, but when I try to connect from another machine on the same network, the connections is refused, even though Windows Firewall is disabled.
I am able to connect to and browse the shared folders on the server using Windows Explorer, so it is not a physical connection issue. I can ping other machines on the network from the server, but trying to ping the server from another machine results in "Destination host unreachable".
As far as I can tell, the server refuses any TCP connections from any machine. I am thinking, there must be some other configuration setting that I am missing... Please, help.
NS
Like in Windows 7 the behaviour is determined by the network type (home, work, internet) the OS thinks it is connected to... even with a disabled firewall it respects these settings and accordingly refuses/allows connections...
The solution is embarrassignly simple, and the credit goes to Ashley Steel, on ServerFault.com for asking just the right questions. It turns out that the DNS was resolving the name of the server incorrectly, because the machine was named the same as an old, since decommissioned workstation that used to live on the same subnet.
The solution: rename the server.
NS[Now hiding under a rock]