[quote="cgrafx"]Thought it might be related to Network Discovery settings, but thats not it.

All the tablets are running Win10 Pro, but the one tablet with the issue is on a newer release of windows (22h something) rather than (19 something). I did read something about SMB1 on XP and SMB2 running on windows 10 and having to enable SMB1 support (which may be enabled by default on the earlier win10 releases). I haven't checked that yet, but will report back if that works.

May end up having to revisit this entire issue again when I upgrade host system to my newer motherboard which is running win10. I've been hesitant to move to the new motherboard because I'm not thrilled with the case its installed in (was trying to reduce weight and purchased a lightweight aluminum 2u case). The build quality is questionable and it has really limited airflow on the top of the CPU cooler. I have been using 65 watt CPUs which fit really nicely in a 1.5u case, but decided to try a faster chip with 125W TDP, but it makes the entire CPU stack taller. Even with a super skinny CPU fan, there is only a 1/8-3/16in gap between the cpu fan and the top case cover. So will either have to drill cooling slots in the cover, or swap the cpu with a lower TDP part, which should allow me to reuse the 1.5U steel case. Its heavier, but way better build.[/QUOTE]

Unfortunately that wasn't it. :(

Since I can connect with the IP address, I'm not going to spend anymore time on this. It's all likely to change once I upgrade and move my host system to Win10 anyway.

Just one of those annoying things.

Thanks all for bearing with me.

[size=100]Philip,

This "[I]SMB thing[/I]" does bring back [I]some interesting memories[/I] of issues that I was having with SAC Remove and Windows 10. SMB should be enabled.

Control Panel > Programs and Features > Turn Windows features on or off > SMB 1.0/CIFS File Sharing Support [Enabled]

I do believe that should do it!?!

I do hope that this tid-bit helps?
[/size]

Thought it might be related to Network Discovery settings, but thats not it.

All the tablets are running Win10 Pro, but the one tablet with the issue is on a newer release of windows (22h something) rather than (19 something). I did read something about SMB1 on XP and SMB2 running on windows 10 and having to enable SMB1 support (which may be enabled by default on the earlier win10 releases). I haven't checked that yet, but will report back if that works.

May end up having to revisit this entire issue again when I upgrade host system to my newer motherboard which is running win10. I've been hesitant to move to the new motherboard because I'm not thrilled with the case its installed in (was trying to reduce weight and purchased a lightweight aluminum 2u case). The build quality is questionable and it has really limited airflow on the top of the CPU cooler. I have been using 65 watt CPUs which fit really nicely in a 1.5u case, but decided to try a faster chip with 125W TDP, but it makes the entire CPU stack taller. Even with a super skinny CPU fan, there is only a 1/8-3/16in gap between the cpu fan and the top case cover. So will either have to drill cooling slots in the cover, or swap the cpu with a lower TDP part, which should allow me to reuse the 1.5U steel case. Its heavier, but way better build.

Most likely there is a missing name resolution service on the one that does not work... I don't remember all the network services that need to be running for that to work, but it probably has to do with a service on the one not working that is not active.

Bob L

[size=100]Philip,

If i understand "[I]things[/I]" correctly, you have three tablets, two "[I]non-pro[/I]"...and one..."[I]pro[/I]"...correct?
[/size]

I know this isn't helpful, but in my own experiences with Win10 and (even) Win7, I haven't been able to get any of the Win10 pcs to cooperate with the network at home... the only one that consistently sees and connects to all the others is the single Win7 pc I still have to use as an office computer. I keep it active for just that reason, in fact. Sometimes I can get three or four pcs to see each other, but rarely, if ever, can I actually connect to share files, even though they all show up at the time.

As for SAW and the tcp remoting I used to love to do, I gave up when switching the studio and upstairs "server" pc (which serves as an entertainment system hub) to Win10 a few years ago. I tried on and off for several months to regain the remote functioning with SAW, but Win10 wouldn't cooperate, no matter what I tried. I think it worked a few times, but never consistently. This is with a Win10 Pro and Win10 LTSC os pairing.
I really miss it.

Hope you find a solution.

Ok, I had some downtime and wanted to make sure all 4 of the surface tablets would connect to my live rig.

I had a few mismatched software revs between 4.6x and 4.7.

So I updated the SAC system to 4.7, updated all of the surface tablets versions to 4.7 and all of them connect and work properly except for the one surface pro tablet.

I can get the tablet to connect if I put in the IP address of the host, but get a "host not found" error if when I try and just use the Name of the Host system.

keep in mind the host name works on the other three tablets.

I've checked, the IP configuration of the wireless connection, made sure the system is on the same WORKGROUP, and I don't have any firewalls running.

I'm not sure where else to look at this point, but thought I'd through this out to the community to see what ideas everybody else might have.

Host is running WinXP
Tablets are all running Win10 Pro