Network access with windows 10 pro version 1809

I am attempting to install a new lap top on a Server 2008R2 network.
The laptop is running Windows 10 version 1809

I was able to connect to a wireless network and browse shared devices.

The network I need to attach to does not have a wireless option.  The DHCP server assigns the IP address that is reserved for the laptop to the laptop.

I am able to connect to the internet [as I am forming this question]

When I go to network and attempt to either browse to shared files on another computer or join the domain, I get "the remote device or resource won't accept the connection"

I have enabled both nearby sharing and share across devices with no difference in trying to access shared files
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JohnBusiness Consultant (Owner)Commented:
First, I no longer have any Server 2008 machines to test. It is out of support and needs to be replaced.

Now, look in Control Panel, Network and Sharing Center, Advanced Sharing Settings.

Be certain you are on a Private and not Public Network. This is the first thing.
Then make sure Network Discovery and File/Print Sharing are both ON.

Then on the Server, make sure SMBv1 is disabled and SMBv2 is running.

Check these things and please let us know.  I am running V1809 fully updated and it works fine on Server 2012 and above.
WilfAuthor Commented:
The server will be replaced in about 3 weeks with Server 2016.

It is a private network and network discovery and File/print sharing is on

Is there any method other than PowerShell to determine what if any SMB protocol is in use on the server?  

My main object for this laptop is to connect to a printer on the network.  It works will connect peer to peer with wireless, but not with ethernet
JohnBusiness Consultant (Owner)Commented:
Follow the Microsoft Article below and adapt if necessary to disable SMBv1 and enable SMBv2
Price Your IT Services for Profit

Managed service contracts are great - when they're making you money. Yes, you’re getting paid monthly, but is it actually profitable? Learn to calculate your hourly overhead burden so you can master your IT services pricing strategy.

JohnBusiness Consultant (Owner)Commented:
It works will connect peer to peer with wireless, but not with ethernet

Also, upgrade the Wired Ethernet driver in Device Manager.

If necessary run TCP/IP Reset

Open cmd.exe with Run as Administrator
Then: netsh int ip reset c:\resetlog.txt
Then: ipconfig /flushdns
Then: restart the computer
WilfAuthor Commented:
I did the PowerShell commands, but nothing changed.  I will do the registry edit later today.  I will create and SMB1 with a dword value 0 and an SMB2 with a DWORD value 1.

The netsh made no difference.  I also tried a new workstation that is version 1803, and it cannot connect to anythihg either - same error.  We may need to wait until the new server is here in order to connect anything.

I will reply later
JohnBusiness Consultant (Owner)Commented:
If both V1803 computer and V1809 computer (different computers) will not connect, it is then a Server 2008  issue.

Try the registry edits (be sure you can reverse them).
WilfAuthor Commented:
It did not make any difference by adding the SMB1 as a 0 and the SMB2 as a 1 as Dwords in the registry.

I think we will probably just wait for the new files server because the rest of the Windows 7 computers seem to be working fine.
JohnBusiness Consultant (Owner)Commented:
There must some other issue with the Server but newer servers work great with Windows 10
WilfAuthor Commented:
Thanks for your help on this.  Confirming that it is a server issue has solved my immediate concern, and I am sure all will work once the new server is here.
JohnBusiness Consultant (Owner)Commented:
Thank you for the update and new servers are great with Windows 10
yo_beeDirector of Information TechnologyCommented:
Not sure how the suggestion awarded is a solution.

If there is no solution no points should be awarded.
David Johnson, CD, MVPRetiredCommented:
It has nothing to do with SMB1
Server 2008 has SMB2

What I have to do is disable ipv6 by unchecking the ipv6 settings for the purpose of domain joining, later on I can re-enable it. Windows 10 prefers ipv6 over ipv4 so if ipv6 is not configured properly i.e. dns settings you will not be able to join the domain

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
I have to clear up two things here.

First, 2008r2 is still supported until 14th January 2020. It works with W10, usually without any issues.

Second, switching off SMBv1 cannot solve an issue at all. Though it should be done from a security standpoint, disabling either has no effect or introduces new ones.

On the other hand it is a reasonable decision to await the already scheduled server replacement. But there is no guarantee that it will work then.
WilfAuthor Commented:
I have cleared the check box for IPV6 on the network adapter properties, and still cannot either access the server or join the domain.  I have ran the prefer ipv4 over ipv6 from " " and still have the same results.  When I try join the domain I get an error that "a domain by that name cannot be found"

The version of windows 10 is 1803 that I am trying to join to a Server 2008 R2.  The DHCP of the server is assigning an IPV 4 address to the workstation.  The workstation does not appear in network on any other machine even though the settings in services are set to allow it to appear
yo_beeDirector of Information TechnologyCommented:
Not sure if this is your case, but if you are running your domain functioning level 2003 it might be the root cause.

I found this
WilfAuthor Commented:
The domain is running at 2008 level.  I found an error in the DNS, and then clearing the check box for the IPV6 seemed to allow the connection
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.