F5F Stay Refreshed Power Users Networks NetBIOS over TCP/IP connection linking Windows 10 Pro with Windows NT in identical or varying workgroups

NetBIOS over TCP/IP connection linking Windows 10 Pro with Windows NT in identical or varying workgroups

NetBIOS over TCP/IP connection linking Windows 10 Pro with Windows NT in identical or varying workgroups

T
Tim9810
Member
Find
231
09-30-2016, 11:08 AM
#1
I'm trying to swap out a particular device for security reasons, even though it requires a parallel port license key. It seems like everything is functioning except the final step, which involves installing outdated software on a Windows Server 2000 system from its predecessor. The challenge lies in getting these two systems to talk to each other. The Windows Server 2000 uses netBIOS over TCP/IP for SMB communication with another Windows NT machine. It also has a network share within its own workgroup that links back to the NT machine, which is likely operating on the same VLAN and passing through one or two switches without any firewall blocking.

The toughest part is figuring out how they interact since the NT machine lacks a usable IP address. My guess is they rely on netBIOS over TCP/IP for communication, allowing the Server 2000 to reach the NT machine across the VLAN, probably through one or two switches.

Another issue is connecting the Server 2000 to the new Windows 10 Pro machine via netBIOS, which works perfectly. I suspect the problem is how the Server 2000 communicates with the older Windows NT system. I've confirmed the connection in both directions, but I'm still puzzled about why it fails specifically between these two machines.

I've reviewed the host entries without success and haven't found any clues about cross-workgroup connections. The new machine (cpc3210) can see the old one (cpc32), but not the HD server (hds). My aim is to connect to hds090000544244, and I think the cpc32 link shows SMB1 support is active.

The path appears consistent, but I'm unsure why this setup works while others don't. I've set up group policies to enable SMB1, adjusted sharing settings, and turned on Functional Discovery Services. I haven't tried reusing the old machine's name and MAC address, but I might give it another go since it was the starting point.
Reply
Reply
T
Tim9810
09-30-2016, 11:08 AM #1

I'm trying to swap out a particular device for security reasons, even though it requires a parallel port license key. It seems like everything is functioning except the final step, which involves installing outdated software on a Windows Server 2000 system from its predecessor. The challenge lies in getting these two systems to talk to each other. The Windows Server 2000 uses netBIOS over TCP/IP for SMB communication with another Windows NT machine. It also has a network share within its own workgroup that links back to the NT machine, which is likely operating on the same VLAN and passing through one or two switches without any firewall blocking.

The toughest part is figuring out how they interact since the NT machine lacks a usable IP address. My guess is they rely on netBIOS over TCP/IP for communication, allowing the Server 2000 to reach the NT machine across the VLAN, probably through one or two switches.

Another issue is connecting the Server 2000 to the new Windows 10 Pro machine via netBIOS, which works perfectly. I suspect the problem is how the Server 2000 communicates with the older Windows NT system. I've confirmed the connection in both directions, but I'm still puzzled about why it fails specifically between these two machines.

I've reviewed the host entries without success and haven't found any clues about cross-workgroup connections. The new machine (cpc3210) can see the old one (cpc32), but not the HD server (hds). My aim is to connect to hds090000544244, and I think the cpc32 link shows SMB1 support is active.

The path appears consistent, but I'm unsure why this setup works while others don't. I've set up group policies to enable SMB1, adjusted sharing settings, and turned on Functional Discovery Services. I haven't tried reusing the old machine's name and MAC address, but I might give it another go since it was the starting point.

Reply
Reply
B
BlueWizard11
Junior Member
Find
30
10-01-2016, 01:21 PM
#2
It's possible you discovered something related to the NetBEUI protocol, which can be tricky to activate on Windows 10.
Reply
Reply
B
BlueWizard11
10-01-2016, 01:21 PM #2

It's possible you discovered something related to the NetBEUI protocol, which can be tricky to activate on Windows 10.

Reply
Reply