I need your help. I am trying to completely avoid connecting my windows server 2012 r2 with an existing Squid proxy server.
I tried the following:
Netsh winhttp show proxy -> answer DirectAccess???
In the LAN settings, the automatic detection and proxy options are turned off
Registry:
I deleted the keys(predefined proxy settings) under:
"HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections
DefaultConnectionSettings and
SavedLegacySettings
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings ( ProxySettingsPerUser value set to 1)
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\Connections keys deleted
I have tried to disable and enable HKLM\System\CurrentControlSet\Services\WinHttpAutoProxySvc settings but unfortunately it didn't help.
I have deleted cached files under: C:\Windows\ServiceProfiles\LocalService\winhttp
I have deleted the sub key under HKEY_USERS\S-1-5-19\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Wpad
Yet somehow my host still connects to the proxy server in the background. I really don't know what to do next.
Internet explorer does not connect to the proxy server, but I can see the following in the background in the access log:
I have two network adapters, one is LAN and one is Microsoft Hyper-V. In the Proxy access log it says that my first adapter try connect with second one.
xx.xxx.xxx.01 TCP_MISS/503 3677 POST http://xxx.xxx.xx.02:8080/gofrom/RPC2 - DIRECT/xxx.xxx.xx.02 text /html
Do you have any idea? Thank you in advance!
I have found a solution.
WinHTTP Web Proxy Audo-Discovery service must be disabled and stoped.
Under %systemdrive%\Windows\System32\Drivers\etc\hosts
Create the following entry for WPAD in the host file: 255.255.255.255 wpad.
Delete cached files under: C:\Windows\ServiceProfiles\LocalService\winhttp if they exist.
Of course, all registry keys in the above post must be deleted and after that a new start of the SERVER is required. Please first export and make registry backup file.
Related
I have used windows 2008 AD since 2013.and I have secondary domain as well. unfortunate due to hardware failure the primary domain was corrupted. I configured a new AD on windows 2012R2.now my concern is when I restart my primary domain it giving many errors. "Naming information cannot be located because: The specified domain either does not exist or could not be contacted. Contact your system administrator to verify that your domain is properly configured and is currently online."
It will automatically resolving when I switch on the secondary domain.
Now what I want to do , I need to resolve this error..
Which server holds the FSMO roles? Are both servers Global Catalog and DNS servers?
What is the status of Sysvol.Go to Registry editor and open the key SysvolReady at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
Hi this is a known issue.
These issues may occur if TCP/IP filtering is configured to permit only port 80 for TCP/IP traffic.
And you can consult the link for a possible solution
I have a shared folder on a windows 10 host machine. I could access it from a windows 10 client machine, where I had set "remember credentials" when first accessing the share. I changed the password on the host. Now the client cannot access the shared folder. That was expected. But I could not find a way on the client to allow the user to re-establish access to the shared folder.
I expected it would ask for credentials again. However I got a network error saying that windows cannot access the host machine.
Based on a number of entries on various forums, I tried a few things. The credentials manager on the client does not show the host. I stopped and restarted file and printer sharing on the client, without any change in the result. Network diagnosis and the windows troubleshooter gave no help.
The problem was due to some previous connections remaining in the network table, even though disconnected, as presented by the "net use" command from the command prompt.
>net use
Status Local Remote Network
--------------------------------------------------------------------------
Disconnected \\192.168.1.71\IPC$ Microsoft Windows Network
Disconnected \\HOST\IPC$ Microsoft Windows Network
After deleting them (via "net use /delete") the next attempt to access the host asked for credentials. Yay!
I began the path to the solution when I tried
net use z: \\host\shared /user:admin password
which gave system error 1219 stating multiple connections to a server are not allowed. Disconnect all previous connections and try again. Obviously, even though known to be disconnected, the entries prevented reconnection.
I am using Windows 2012 R2 VM machine in Azure. I have read multiple article to setup Filezilla server in this environment. However, I am not successful. Any one faced this issue? Any solution will be greatly appreciated.
Just remember to add Filezilla to Windows Firewall :-)
I'm dealing with the same thing right now. locally the FTP serv works great. remote I cannot establish a passive connection. Based on my research this is because Azure is not set up for Passive-FTP. I am uncertain if we can get FileZilla to operate in a active-FTP mode. Will post back if I ever get to the bottom of it. Mine currently connects and authenticates but 'cannot retrieve directory listing' when it tries to kick over to passive (transfer) mode.
In addition to checking the Virtual Machine endpoints are open, be sure to also add the appropriate Windows Firewall rules if you have Windows Firewall enabled on your Windows VM.
Yes, We can connect to Azure server via FileZilla Client.
Steps:
Login to Azure portal: https://portal.azure.com
Click on App Services.
Select the Site and then click on Get publish profile.
Save the file and open it in notepad.exe.
The file contains 2 <publishProfile> sections. One is for Web Deploy and another for FTP.
Under the <publishProfile> section for FTP make a note of the following values:
publishUrl (hostname only)
userName --------------------------> This is the information you are looking for
userPWD
Add the PublishUrl to Hostname, Username and password in their respective fields.
Connected.
The link will give the detailed description of the steps flow with images.
Here is the link.
Thanks
My OS is windows7 64 bits.
I'm in a corporate environment. In order to have internet connectivity I have IE configured to use a automatic configuration proxy script.
Additionally I connect into an external company dial-up VPN (via internet). When connecting into the VPN I see that my hosts file are modified and the route print is changed too. The VPN dial-up connection uses another proxy automatic configuration script (under dial-up and VPN settings).
I'm able to see the contents of the two automatic configuration scripts as well as the route print info.
I have a .Net1.1 winforms app that uses WebClient to download an xml file from a web server.
When connected into the VPN:
The winforms app is not able to download the file ("server cannot be reached" error).
If I browse to the same URL within IE I'm able to download the file.
Moreover when I start Fiddler to inspect the http sessions, the winforms app is able to download the xml file.
Running netsh->proxy, system32 and SysWow64 versions show Direct access.
I suspect the problem is somehow related to proxy configurations but I don't know where to look first.
Any help on putting things in order would be really apreciated...
The problem could be a result of TCP tuning on you windows7 machine. Try the following then restart your computer.
Click on Start button.
In the Search box, type in Command Prompt. Command Prompt will show up in
the search results.
Right click on Command Prompt icon and select Run as administrator.
Enter the admin credential and you are ready to go.
Once you get to the elevated command prompt:
Type all the commands below and click enter after each one.
netsh int tcp set global autotuninglevel=disabled
netsh int tcp set global autotuninglevel=disabled
netsh interface tcp set global rss=disabled
netsh interface tcp set global autotuninglevel=disabled
netsh interface tcp set global congestionprovider=none
Just for reference,
It turns out that .net framework 1.1 WebClient doesn't understand automatic proxy configuration within its defaults settings:
<system.net>
<defaultProxy>
<!--
The following entry enables reading of the per user (LAN) Internet settings.
Adding additional proxy settings, without first setting to "false",
will individually override. Note that "Automatic configuration" and
"automatic configuration scripts" cannot be read.
<proxy> settings:
usesystemdefault="[true|false]" - Read settings from Internet Options (see above)
proxyaddress="[string]" - A Uri string of the proxy server to use.
bypassonlocal="[true|false]" - Enables bypassing of the proxy for local resources.
-->
<proxy usesystemdefault="true" />
</defaultProxy>
</system.net>
One posible workaround is to manually add the proxyadress in the config file
<system.net>
<defaultProxy>
<proxy usesystemdefault="false" proxyaddress="http://myproxy:myport" />
</defaultProxy>
</system.net>
I've installed TFS 2008, but I can't seem to access the server. When I try to connect to it in Visual Studio, I can't. If I try by browser on a remote PC, I get a generic page cannot be displayed. On the server, I get a 403. Nothing was touched in IIS and the service is running as a Network Service. Any ideas?
try:
http://localhost:8080/Services/V1.0/ServerStatus.asmx. This will tell you if TFS is up and running. If you are getting anything else you need to look into IIS issues.
I wrote a blog post on diagnosing these types of TFS connections.
http://blogs.msdn.com/granth/archive/2008/06/26/troubleshooting-connections-to-tfs.aspx
The very first thing I do is confirm that it works for a known-good configuration – usually my workstation.
Providing that works and the server appears to be functioning, the next thing I do is ask the user to call the CheckAuthentication web service using Internet Explorer.
The URL for this is: http://TFSSERVER:8080/services/v1.0/ServerStatus.asmx?op=CheckAuthentication
By doing this check, I am doing four things:
Eliminating Team Explorer from the picture
Eliminating the .NET networking stack from the picture
Ensuring that Windows Authentication is working correctly (that’s why I say IE)
Ensuring that proxy settings are set correctly
In most cases I’ve seen, the TFS connection issues are because the proxy settings have changed or are incorrect. Because .NET and Visual Studio use the proxy settings from Internet Explorer, it’s important to have them set correctly.
In rare cases it’s beyond this. That’s when I start looking at things like:
Can you resolve the server name?
Can you connect using the IP address?
Are there HOSTS file entries? (see: c:\windows\system32\drivers\etc\hosts)
Can you ping the server?
Can you telnet to port 8080?
Does the user actually have access? Run TfsSecurity.exe /server:servername /im n:DOMAIN\User to check their group memberships
Have you changed your domain password lately? In some cases they’ll need to logoff the workstation and log back on again to get a new security token.
Is the computer's domain certificate valid? update the certificate: gpupdate /force
Hope this helps.
Turns out the time and date on my computer was not "close enough" to the time and date on the tfs server. Changed my system clock setting and problem went away.
What happens if you send a simple HTTP request to the server directly?
ie:
telnet 8080 [enter]
GET / HTTP/1.1[enter]
[enter]
[enter]
That might give a hint about whether IIS is actually serving anything. If you can do that on the server, what about from a different machine? If the results are different a good guess is there are some security/firewall issues somewhere. HTH a little.
I went through everything on a similar problem.
I logged onto my tfs server and connected directly there.
I also used a TFS admin tool I downloaded some time ago from Microsoft, and made sure I was in all the right groups and projects.
I then went back to the client PC with the problem, tried the services/1.0/serverstatus.asmx?op=CheckAuthentication Url again, and it worked this time.
AFter that full service was restored to my PC.
So I don't have the exact answer, but I would go through the checklists presented by Grant Holliday in his answer.
Add this to the cases for future users, as i had this issue on server 2016...
if your firewall allow only Domain and Private Network, it may not work on client. make sure you give public permission, if server network is set to public...
The error you may face:
ERR_CONNECTION_TIMED_OUT
for
http://fserver:8080/tfs