So, I have purchased a VPS from a service provider and wanted to access it by using Microsoft RDP client. I have been doing this for a while so I am familiar that you have to enter the IP Address, then the client prompts you to enter the username and password which is usually provided by the service provider and than you are logged in.
However, in this case, when I enter the IP Address, a new kind of screen pops up that mentions 'XRDP' and looks something like below:
xRDP
I have no idea what this is but still, I enter the username and password provided by the service provider and hit 'OK' and this is what it shows next:
XRDP
Now, I have been in constant contact with the service provider and they have been helping and saying that they can connect to the VPS easily using the same microsoft RDP and do not see anything like I have been seeing and that the issue is on my end and not theirs.
I have another VPS from a different service provider and that is working fine but this one does not. Can anyone help? I have tried reinstalling the VPS several times but that does not work either. I have tried researching about XRDP too but did not understand anything.
Related
The entire scenario of my situation seems 10/10 sketchy, I'll admit. So I won't bother convincing you this isn't a malicious attempt to access a server that isn't mine - I'll simply say once, that this is a legitimate need for assistance.
That said, basically my problem goes back to me being a little too restrictive when it came to SSH access to my CentOS 6 server. Basically I restricted access to my custom SSH port from only two IP addresses - one being my home address, and one being my work address - via iptables. The problem is, I no longer work where I do, and my home IP address changed ever since I upgraded my internet.
Obviously this means I no longer am able to connect to my server via SSH since I don't own that IP address anymore.
My question is, is there anything I can do to access this server? I have no console access, but I do at least know the IP address I used to use to log into the server (maybe possible to spoof an IP address, but I have no clue). The only other thing I can think of is I have DirectAdmin installed on the server and can still login with the admin account. Other than that, I've got nothing.
If anyone has any idea on what I can do, it would be greatly appreciated.
You can change the SSH port number from Directadmin file editor (if you have root password),
Then restart the sshd service from service manager
And you can connect to SSH via new port number!
I rented a server for a month to try some things out. I'm fairly new to servers and everything and trying to learn. I now want to have projects on this server using VisualSVN.
I've installed VisualSVN and added some users to gain access to these repositories. However, everytime I try to login, the authentication window keeps popping up (no matter what I fill in as a username and password).
How do I solve this issue? I'm unable to connect to the repository due to the login window popping up forever after entering the username and password.
I've been having the same issue! (RESOLVED!!!)
The way I fixed the problem was to change some firewall settings on the server.
If you go into windows firewall settings and make two new "rules" (one for inbound port 443 and one for outbound port 443), you should be good to go. Allow the connection for all networks (public, private, etc.).
After I changed this, I only had to authenticate once and checkout worked fine.
Let me know if this works!!! This problem was killing me.
The basic issue is in IE on my machine, a particular web site in our intranet doesn't work when using the server name alias. It does, however work when using the IP address of the server.
This doesn’t work
http://MyWeb/TheSite
It's a 401 error in the IIS Logs on the server
and IE shows "Internet Explorer cannot display the webpage. Diagnose Connection Problems".
But this does work:
http://100.100.100.100/TheSite
(100.100.100.100 being a made up IP)
On other machines on our intranet, this does work for me:
http://MyWeb/TheSite
I think we've narrowed it down the Integrated Auth on IIS. When I change the AppPool for MyWebb/TheSite to Anonymous on the server, TheSite works on my machine as well as other machines. When I change back to Integrated Auth it works for me on other machines machines but not my machine. Any ideas? Something with my desktop profile?
And another bit of data, TheSite used to work on my machine with Integrated Auth. It just stopped a couple weeks ago.
Also, we've looked at all the relevent DNS properties, etc, and that all looks good
using IIS 6
I have the default web site that works and can authenticate users to the domain when they connect.
I have created a second website, siteb, put a host (a) record into DNS, I can browse to it as long as I have use anonymous access, when I select windows authentication, it fails...
not sure what i'm missing here...
Thanks.
This goes beyond just IIS if you're using Integrated Windows Authentication. You've created "siteb" in DNS which allows your users to connect to it so this is good. However, when their browser requests a Kerberos ticket for "siteb" from Active Directory, AD is probably responding that it cannot find "siteb". You can verify this with Wireshark.
The fix is to add "siteb" (and any other permutations with which you expect users to access the site) as an additional servicePrincipalName for the server's machine account in AD. You can accomplish this with the "setspn.exe" utility. It should be available on your domain controller. If not, you can install it from the Windows 2003 Support Tools.
Some examples of adding a UPN alias with setspn on the DC are:
setspn.exe –A HTTP/siteb <server hostname>
setspn.exe –A HTTP/siteb.acme.com <server hostname>
This should take effect immediately. The final step is ensuring that the browser "trusts" the new website name. In Internet Explorer, for IWA to occur automatically, the server name should be listed in either the Trusted Sites or Intranet zone.
Of course, you could avoid all this hoopla by having the 2nd website just run on a different port under the same name, e.g.: http://sitea:81
I'm having a bizarre issue where I'm hitting a WCF service on a remote machine (still in same domain) and it's saying I'm logged in as someone else. On the client side, if I check the Principal.WindowsIdentity.GetCurrent(), it says I'm "COMPANYNAMEHERE\Albert". But when it goes over to the server side, it says I'm "COMPANYNAMEHERE\Albert_Admin". I've had 3 other users test the service and they authenticate fine, it's just me that has this issue.
I've had other devs log onto my machine and they're fine. I've hit other WCF services as my account with the same problem.
The IT folks are stumped, as am I. Anyone out there know what might be causing this?
Turns out something in my local desktop profile (I don't know what) was causing integrated security to resolve me as my _Admin account. I had tested my login on a co-worker's machine and everything worked fine. So my network admin suggested I wipe out my local profile and that seemed to do the trick.