Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 67
  • Last Modified:

Win10 Pro HP laptop connect to WinServer 2012 R2

Call from client, new HP laptop Win10 Pro fails to connect on ethernet to Win Server 2012 R2. Other computers connect fine. Laptop sees internet, can ping the server, but errors with "can not find". Firewall is Win builtin.
Router restart, laptop restarts, ethernet wire swapped, no success.
I did some Googles, suggested some troubleshooting.
Email back from client, he tried Wi-Fi and it connected immediately.
Any suggestions to explain this?
0
David Anders
Asked:
David Anders
1 Solution
 
CompProbSolvCommented:
Is the wired connection using DHCP or are the parameters set statically?

When connected wired, are you pinging the server by name or IP address?

Also, turn off IPv6 on the laptop and see if that changes anything.
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
DNS Settings.  Problems connecting to the server are 95% of the time DNS related.
1
 
Dillyn BarberChief Information Officer (CIO)Commented:
If your client can connect with WiFi but not with LAN it sounds like this article may help:
https://superuser.com/questions/698275/website-is-accessible-via-wifi-but-not-lan

They also need to verify that their IPV4 settings are exactly the same as their WiFi network adapter as it is for their LAN network adapter / change their dns for that adapter to rule out a dns issue. (8.8.8.8, 8.8.4.4)  <- Google's OpenDNS
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
John HurstBusiness Consultant (Owner)Commented:
Windows 10 connects just fine to Server 2012 R2. No issues on any Windows 10 machine.

In addition to the above (but I do not recommend disabling IPv6 at all) try a TCP/IP reset and DNS flush.

Open cmd.exe with Run as Administrator
Then  netsh int ip reset c:\resetlog.txt
Also, ipconfig /flushdns followed by net stop dnscache followed by net start dnscache
Then restart the computer
0
 
CompProbSolvCommented:
The point of disabling IPv6 was as a test to see if the issue was v6-related.  I've seen misconfigured IPv6 on the server causing similar problems.  If disabling IPv6 on the workstation causes the problem to go away, it makes it clear where the troubleshooting needs to go next.
0
 
David AndersTechnician Author Commented:
Client emailed that a third ethernet cable solved the problem.
Thank you for your suggestions.
"If the problem involves a cable, suspect the cable"
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now