hi bigbearjedi
thanks for your response Ill give back drop laptop was done via the upgrade straight from windows 8.1 it in its own workgroup as with out professional or above on it it will not connect to my AD. Ad that is running is a 2003 incarnation the pc running as my server is also using server 2003. I also have A tp-link 8 port 1000gb hub. My internet comes in via Virgin superhub which is the wireless router. Both this and server and pc laptops are on the same subnet. Super hub is also connected to the Tp-link hub
>>>Thanks for your response back, this information does help some. I'm still confused by how you have everything connected. Did I understand you to say you have 2 computers running 2003 Server software on this network? If this is the case, it's no wonder W10 is confused about trying to access folders on your Main server. It sounds like you have some network knowledge, however, you cannot run two-2003 servers in the same domain; one has to be subjugated to a secondary server on the same Domain. So that's never going to work, with W10 or earlier Windows versions that are domain-capable.<<<
All devices on the network have static IP address. There is also a DHCP range for the wireless again on the same subnet. My new laptop is an ultrabook so it has no network port so connects via the wireless.
>>>I see that this is really a cobbled together system, and that may have worked for you in the past, however, in the business world mixing static IP's for wired ethernet and DHCP for wireless went out over a dozen years ago. This is usually only done when the Tech repairing or installing the network is not familiar with how to do things properly, or has a limiting piece of hardware--often a cheap switch or hub being forced to do the work of an intelligent switch or router. If you indeed have two 2003 servers in the same domain, you'll need to replace your TP-link hub with an intelligent auto-switching router or hub, and re-address the secondary domain onto a 2nd subnet. Often a secondary domain server is an app server such as a web server, an E-mail server, or a SAN (Storage Application Network) server. This can pose a security risk, if the secondary domain server is physically located in another building in another city, state, or country than the Primary Server. You've ignored this particular design rule for convenience, but it's not how it's done in the real world. If I've misunderstood you, and you only have 1 Primary Domain server, then you need to explain better to us how you have it connected. At this point, you've cobbled together a server in a home environment which really isn't being used correctly. You might as well just use that thing for a NAS box or a stand-alone storage device. That's how I used mine, since my Vista Home won't work with my Server on the Domain. Also, my 2008 server just died. I turned it on and was going to do some testing on remote login, but it's dead and I have to fix it. That's probably going to be a few months if parts are required and available.<<<
At the moment all devices can see each other weather they are a physical connection using a static IP or wireless using a DHCP address. my laptop which is not connected to my domain can only communicate via its IP address and not my dns names
>>>I understand. Going back to my initial analysis of your network, this is why you are having trouble using folder share names and FQDN's with the W10 as I said; the version you have is non-Domain compliant so this pretty much explains why your other devices are working on the Domain and the new laptop is not part of the conversation. Generally, it is considered poor design form to mix Workgroups (which is really the poor-man's peer-to-peer LAN) and a Domain server. This is usually only done in very large networks; 4 computers does not comprise a large network with hundreds or thousands of machines. If one must mix Workgroups into a Domain environment due to legacy servers or older machines, then it must be done properly. Repeating again, you either get an intelligent switch or router to replace your hub, and put your W10 laptop in a Workgroup onto a separate subnet or not, that's up to you. But, if you are doing what I think your are doing, you'll need to upgrade your W10 to a version that supports Domains, period. W10 Pro, W10 Business, & W10 Enterprise are your only choices at this time. These versions start at $199 US to about $1300 US per seat. These are very expensive and not designed for home use, which you are attempting to do without spending any money to make things work correctly. I get that; I did exactly the same thing with my 2008 server. You'll have to redesign your network, make some changes (switch/router), and Domain redesign if using two machines running 2003 server, and your version of W10 running on that laptop. You might be able to do this for under $500 or so, maybe less. Is it worth it to you, that's the question you have to ask yourself.<<<
Only issue is the laptop which is my only windows10 device will not allow me to see any of sysvol folders on my server it can other folders fine. It was also working fine on windows 8.1 so this is an issue with windows 10. Now I'm lead to believe that windows 10 has now disabled guest account, which I've read has caused lots of issues with NAS boxes which where not set-up properly and where using this account to gain access not sure if not being on the domain maybe mine was. I have not tried the reg hack to enable this. Since really this should not be enabled bit of a security risk.