OS X 10.12.6 with Chrome (70.0.3538.0) and Office for Mac 2011 (14.7.7) and attempting to edit a document with WebDAV using it Hit Ajax Library (2.0.1773.0) & WebDAV Server (4.0.2416.0) returns this error "No connectivity with the server...The file 'https://................' can't be opened because the server couldn't be contracted" and the file is not opened to edit...when connecting to a server using HTTPS but connecting to another server using the same it Hit software using HTTP opens the document, allows editing and saving back to the server.
This command was run with Terminal (defaults -currentHost write com.microsoft.registrationDB hkey_current_user\hkey_local_machine\software\microsoft\office\14.0\common\internet\basicauthlevel -int 2)
What other setting do I need to change on OS X to allow itHit Ajax Library (2.0.1773.0) & WebDAV Server (4.0.2416.0) to use both http and https connection to the web site...
Related
Our file transfer automation software is connecting to an external SFTP server to download files. It's connecting using Putty's command line tool PSFTP. When it kicks off at it's scheduled time, an error results. The error is:
Remote working directory is /directory
lcd: unable to change directory: Invalid Signature.
Using username "username".
Pre-authentication banner message from server:
| IM CCaaS FTP server
End of banner message from server
When I manually FTP to the server, I can log in with no issue. I then re-run the job and it completes successfully. I've googled this and found articles on key exchanges with similar errors, but this connection isn't using private/public keys. I cut over the application to a new Windows 2016 server on September 21st. There have been some successful transfers. I've also read the version of PSFTP may be the issue (0.73), but I would have expected consistent issues connecting. It seems sporadic. I'm not sure if the issue is on my end or at the destination. Any thoughts?
This is not SFTP problem. You have problem when changing a local working directory (using lcd command in the sftp client).
So this probably covers the problem:
System error 2148073478, extended error, or Invalid Signature error message on SMB connections in Windows Server 2012 or Windows 8.
I have a local MAC machine that RDPs into a windows VM. On that windows VM/desktop I have Power BI Desktop installed along with the Cdata PowerBI/Quickbooks ODBC driver (https://www.cdata.com/drivers/quickbooks/download/powerbi/).
On a separate server (which I can RDP into from the virtual machine) I have quickbooks desktop installed (https://www.acecloudhosting.com/) and in single-user mode (opened a company file w/ an admin user). On that server I have also setup QuickBooks Remote Connector (http://remoteconnector.com/), which essentially is used to create an authenticated connection to QuickBooks. This "remote connector" also acts as a lightweight web server that listens for incoming requests (such as a power bi direct query) and uses that to communicate with Quickbooks hosted on a separate server.
However, I keep getting an HTTP protocol error and not sure if it is because the ports are not setup properly or if something in my ODBC connection is incorrect. It is very odd that I can RDP into the remote server from my VM, but when I try to ping the server my request time out despite allowing ICMP responses in the windows file sharing options so I find that odd.
I have worked on this for about 4 hours, but have run out of things to try.
http://cdn.cdata.com/help/RQB/odbc/pg_connectiono.htm
I need to upload a file using ftp or http. I checked downloading from servers like ftp.qt.nokia.com. where download was successful[even though the file(s) downloaded was broken but with almost same size as on Web server]. I tried to upload a file to servers like qt.nokia.com,ftp.trolltech.com. Doing so When I used http, I got an html doc as a response with error count 0,but error string as unkown error. When I used ftp, connection was established, logged in but didn't close connection and again error string unkown error. My point is how can I know that whether my file is uploaded to a server successfully? Can I check it on my own system by setting up a server(for ex: Apache Tomcat server).
Set up a local FTP or HTTP server, you should not rely on any server you don't have full control over. A virtual machine is the probably the most hassle-free solution.
I am trying to connect an ASP.NET 2.0 application hosted on a client machine to an SQL server 2000 instance which is installed on a domain controller running windows server 2003 (I appreciate this is not best practise, but it is something I cannot change). I am using SQL server authentication, not Windows authentication.
During debugging, the following error is displayed at the point the 'connection' is attempted within the web application (not on running any object within Sql Server):
"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)"
I have done some research, and have checked a variety of things:
1) I am certain the conection string is correct - in fact I built a little Windows app that uses the same connection information and connection succeeds...
2) This is limited to the web application - a windows application running on the remote client machine connects just fine using the same connection string (see 1).
3) The firewall settings on both computers do not prevent the connection (see 1).
4) I can ping the windows 2003 server (see 1)
5) The SQL Server credentials definitely have the rights to the objects needed
6) If I (temporarily) put the web application on the windows server 2003 and run it, it loads and runs fine (using a browser on a separate machine, or on the client machine I am trying to connect) - suggesting this is only an issue with a remote connection, and confirming the connectivity between the machines again, and also confirming the necessary security right of the SQL Server user.
7) I can start query analyser on the client machine and using the same SQL server credentials, can run the same queries on the target database just fine.
Stumped. Please help!
You need to go into the SQL Server Configuration Manager and make sure the Named Pipes option is turned on. It is not turned on by default when you install SQL Server.
Because of the research I did in the original question covering the ability of a windows app to connect but not the ASP.NET app to connect from the same machine, and the confirmation the web app was working on the server itself, I was convinced SQL server was set up correctly, that connectivity and firewalls were not a problem - it must have been a difference in the security credentials of the windows app versus the web app.
The windows app runs in the security credentials of the logged on windows user and authenticates using that, whereas the webapp runs in a restricted account and does not pass these credentials over when connecting to SQL server by default. I simply added to web.config, which impersonates the user account within which the web app runs, and it all worked!
Problem solved.
I have an ASP.NET project (VS2008 on Windows 7 with either webforms, MVC1, or MVC2 -- all the same result for me) which is just the File->New hello world web project. It's using the default ASP.NET development server, and when I start the server with F5, the browser never connects and I get a timeout. I tried to debug this by telnetting to the development server's port while it was running, and I got the same result:
C:\Users\farmercs>telnet localhost 54752
Connecting To localhost...Could not open connection to the host, on port 54752:
Connect failed
I can see in the system tray that the server thinks it's running, and a netstat -a -n command shows that there is indeed an active TCP listener on that port.
This worked in the not-too-distant past, and I could work on web projects using the development server. One thing that has changed since then was that I installed the Microsoft Loopback Adapter to accommodate a local development Oracle installation. I'm not sure this is the problem, but it seems a likely culprit.
I also tried to hit the port using the server name itself (http://mycomputername:54752) but with the same result.
So, what could be blocking me from connecting? And if it's the loopback, then what is a good way for me to retain my ability to connect to my development Oracle server while still being able to use the ASP.NET development server?
have you checked your host file?
%SystemRoot%\windows\system32\drivers\etc\host
look if there is any redirection of localhost or 127.0.0.1 to somewhere else rather than your pc