Hi @LeonardHampton-6715 ,
dim oRequest as FtpWebRequest = FtpWebRequest.Create(ftp://xxxxxx.xxx:{customPort})
Have you tried to use ping command to check connection of domain xxxxxx.xxx in cmd? If the domain is public and valid not custom, how did you bind it to server and is there any DNS record in your machine?
Hi @ToddNelson-3704 ,
There's a situation similar to you in this document. IIS hangs on after enable shared configuration.
However, the version of IIS in the document is 7.0 and 7.5. I show it for your reference but you don't have to follow his workaround exactly.
It inspires me that maybe different windows servers cause this issue. In your test, Server 2022 IIS can work well when the shared configuration points to another one which is also 2022. You may try another test, make Server 2019 IIS's shared configuration points to Server 2022. Check if it can work.
Another thing is how you export and import those shared configuration files? If you used web deploy, did the versions of web deploy on Server 2022 and 2019 are same?
Hi @Jess13777-5812 ,
There's a property about certificate called NotAfter. You can get expire date from NotAfter and start date from NotBefore. So as @RichMatheisen-8856 provided, his powershell script can get expire date. You can try it.
Hi @RolandSmith-1025 ,
VS won't use IIS to complie application and run it, it use IIS express. When you stop running, IIS express will auto exit, including w3wp.exe process.
Hi @RolandSmith-1025 ,
Please wait for winsock and C++ engineers to see this question, they will give a more professional answer.
Hi @nhatmvo ,
if I change the timeout of IIS server to higher number, number of issues are reduced,
According to your test result, I think scale up services is a better choice. This can effectively improve the overall server's ability to handle a large number of requests and avoid excessive request queuing. But you can also optimize the speed and queue size of your application processing requests through code. If so, the Q&A community is not a place to offer practical advice. I think the better place is creating a support ticket.
Hi @nhatmvo ,
It's quite possible. Have you tested in production to cancel the ELB and send the request directly to the content server?
Hi @nhatmvo ,
means timeout and status 1236 means network connection was aborted. I think it is very likely that this problem is caused by session loss or expiration. Requests cannot be authenticated when the session is lost, and your production environment will be under high load. This may cause the request to time out. When the data in the request is lost, especially when the session is stored in the server, it will make the server feel that the connection is not secure. Maybe it's because of this that status 1236.
Hi @6666666 ,
First, please try to change the port in solution property and run it again. Then don't forget to Create Virtual Directory.
If it cannot work, please repair IIS express in control panel.
Hi @Studmuffin1134-8970 ,
You mean that they can access server through IP via VPN? If so, VPN is also necessary when access through domain.
Hi @Studmuffin1134-8970 ,
If your friend access the site through domain(not ping), do they have the same issue? When you access it locally, did you access through domain? As far as I know, domain always binds to public IP of server, can you access server through IP directly? It will show default web site on IIS.
Hi @kihyeonkim-0859 ,
Processor item in performance monitor has idle time and interrupt time, you don't need to install it. Please check your monitor again.
Hi @Adrian-2132 ,
Why you want to install IIS on optical drive? IIS is an important program and service on windows server. It is not recommended to change any settings during install it. Please keep all default settings and install it.
Hi @LeonardHampton-6715 ,
Is the TestUser2 a local user or domain user? If it is a local user, you need to make sure it has permissions on the physical folder. Right click the folder and go to Properties. In the Security tab, make sure the user has required permissions. You can ignore Shared tab. It is not used for FTP access. If it is a domain user, make sure the status is unlock and not expire.
The error also may be caused by other permission issue. You can refer to this article to check its permssion. Then check log to get error message.