New answers tagged

0

Well, I was in the middle of writing up a bug report for the PuTTY folks and was reviewing the /etc/ssh/sshd_config on the Ubuntu 16.04 server. It had the line: Subsystem sftp internal-sftp I changed it to: Subsystem sftp /usr/lib/openssh/sftp-server restarted sshd and now everything works properly!


1

Thank you @Greg Askew, NLA is the issue after enabled that, it works.


-1

Then as I said previously, contact the owner of the server for checking if that server has a proper physical connection to ethernet. It could just be a loose cable not allowing all the data to come through. Trust me it happened once


0

Which os are you running this server on. If your running Windows home/pro then contact the server owners for network problems. If you are running server then it makes sense due to the fact that server is meant for shell like usage not graphical usage


1

You'll probably need to manually reconfigure the Windows Time service on the new PDCe and the old PDCe. You can run the commands below in an elevated command prompt on the respective servers to make this change. New PDCe net stop w32time w32tm /unregister w32tm /register net start w32time w32tm.exe /config /manualpeerlist:time.windows.com /syncfromflags:...


1

If your AD replication is working correctly, there is no risk at all; use dcdiag and repadmin to check everything is working correctly before moving a FSMO role, and make sure all DCs are online so that they can properly acknowledge the change. Also, make sure the server that will hold the PDC Emulator role has correct time settings, because it will become ...


1

It's possible to configure iLO to use custom ports, shut down specific connections or filter by authorized list. If you have no idea what the settings could be the easiest recovery is to reset iLO 4 to factory defaults via server setup: From the System Utilities screen, select System Configuration > iLO 4 Configuration Utility > Set to factory ...


1

Can you ping and telnet that IP successfully on 80 or 443? if so then the problem is browser config prohibiting TLS version which you should be able to change.


0

Starting with build 1607, Windows 10 does not allow the "convenience pin" for domain-joined logons by default, out-of-the box. Users who are running Windows 10 Version 1511 or earlier can do so without issue. Note that if you had Windows 10 configured to use a pin or fingerprint sign-in prior to installing the 1607 build, that convenience sign-in ...


0

you could add a new network adapter and bind the new IP-Adress to your site. After that you can use a traffic monitor for the network-adapter. but there is probably a lot of effort behind it... Routings, NAT, etc..


0

You can not do it. You say yourself they all work with the same user account, so the sessions are not "from different people" as far as the computer is concerned. You can also not solve antisocial behavior with technology - you take the people aside and explain them why their services are no longer required. Period. If people do destructive ...


1

I suggest you to use either Azure Instance Metadata Service Invoke-RestMethod -Headers @{"Metadata"="true"} -Method GET -NoProxy -Uri http://169.254.169.254/metadata/instance?api-version=2020-09-01 | ConvertTo-Json { "compute": { "azEnvironment": "AZUREPUBLICCLOUD", "...


4

You'll want to set up another domain controller and migrate the crucial AD roles to it. Then you can demote the old server, reinstall it and set it up as secondary DC. Don't forget to upgrade the AD version to something recent. Of course, you can also install completely anew and start from scratch. That would also mean to set up new user accounts on all your ...


0

You talk abou RemoteDeviceReal and RemoteDevicePublic. So there is something doing NAT between them. Is this router you are trying to configure, or is everything remote (from your point of view)? If everything is remote and you can only see the public IP address of the remote router, there is nothing you can do on your end, whatever OS you are using.


0

Stumbled upon this blog a bit too late... Nevertheless, if you still rely upon any MS Server Media Block (SMB) services (not so mysterious), this service NEEDS to be RUNNING for your device to be advertised on your internal network.


0

If the users are logging to O365 using their Azure AD accounts, then the investigation should start on the Azure AD front, however. It is not clear where the user password verification is happening: If you're using Password Hash Sync: check the current password policies you have on Azure AD: https://docs.microsoft.com/en-us/microsoft-365/admin/add-users/set-...


Top 50 recent answers are included