thandel
asked on
Can not access computers by name
I have 4 VPN connections, all Windows XP computers, one Windows 10 computer. I've been able to access computer shared files by computer name... then one day on the Windows 10 computer I couldn't but can by IP address. The XP computers on the VPN are working fine. There has not been any network configuration changes, NETBIOS is enabled in the router's VPN setup and in the Windows 10 TCP/IP configuration.
Before I resort to editing my host file to make names work again, I would like to resolve why it all of a sudden stopped working. I feel like editing the host file is not the proper solution given all other XP computers are working AND this windows 10 computer was working.
Suggestions are greatly appreciated.
Before I resort to editing my host file to make names work again, I would like to resolve why it all of a sudden stopped working. I feel like editing the host file is not the proper solution given all other XP computers are working AND this windows 10 computer was working.
Suggestions are greatly appreciated.
Sorry, need to add a little more here. Windows XP and earlier utilize the Computer Browser service to determine IP addresses for systems on the same network segment. Windows Vista and later utilize LLMNR caching to accomplish the same goal. For this to work properly, you need to make sure the Windows 10 computer has Network Discovery enabled (Do this from the Network and Sharing center). If you don't have a DNS server in the mix (either using the Router or a dedicated DNS server) it's much more difficult to get name resolution working properly.
Without DNS servers you ha e to either use IPs which might change periodically.
The other possibility you altered the VPN, that previously when setup was sending all requests via the VPN connection, while now only remore lan specific traffic is sent via the VPN connection while everything else goes out the local internet connection.
The other possibility you altered the VPN, that previously when setup was sending all requests via the VPN connection, while now only remore lan specific traffic is sent via the VPN connection while everything else goes out the local internet connection.
ASKER
OK thanks to all, some of the replies I don't follow. So let me reply as best as I can:
Adam Windows 10 and XP were working fine through the VPN via computer names, in fact XP still is. On the Windows 10 computer Network Discovery is enabled for both private and public networks. Can you elaborate on the DNS suffix settings?
Arnold my VPN settings have not changed so I don't think there is an issue there.
Adam Windows 10 and XP were working fine through the VPN via computer names, in fact XP still is. On the Windows 10 computer Network Discovery is enabled for both private and public networks. Can you elaborate on the DNS suffix settings?
Arnold my VPN settings have not changed so I don't think there is an issue there.
Adam addressed one point dealing with how XP resolves cksum outer names.
Check system updates, update history on the Windows 10 system to see whether an update was applied between the last time it worked and now.
Potentially smb1 got disabled and
Setting up a DNS server on the remore site with which those systems register.
In the VPN connection, adding/setting the search domain from the remote location as well as adding the remore DNS server in the list.
Check system updates, update history on the Windows 10 system to see whether an update was applied between the last time it worked and now.
Potentially smb1 got disabled and
Setting up a DNS server on the remore site with which those systems register.
In the VPN connection, adding/setting the search domain from the remote location as well as adding the remore DNS server in the list.
ASKER
2 questions, how do I check the setting for the smb1 and what is smb1?
How do I add the "remote DNS server in the list" and what list are you referring to?
How do I add the "remote DNS server in the list" and what list are you referring to?
On windows 10 advanced firewall settings look at whether Netbios via TCP are permitted.
Look at the VPN setup, DNS settings ....
Look at the VPN setup, DNS settings ....
ASKER
I don't see anything in the firewall should I make an entry to allow and if so inbound or outbond?
VSP is set to enable NetBIOS.
VSP is set to enable NetBIOS.
The ransomeware ware attacking via smb1 had that disabled by msupdate it might be what disabled the Netbios over TCP/ip.
You want to allow in.
You want to allow in.
ASKER
OK but would I setup a rule under inbound or outbound?
Inbound is commonly the one filtered, by default all outbound traffic is allowed, unless and until a specific deny/block rule is added.
Not sure whether advanced setting on the network adapter in Windows 10 have the same option that exist under XP dealing with Netbios resolution where Netbios over TCP/ip settings are..
Not sure whether advanced setting on the network adapter in Windows 10 have the same option that exist under XP dealing with Netbios resolution where Netbios over TCP/ip settings are..
ASKER
I tried creating a rule for inbound and outbound for all ports for all IP addresses and that still didn't help.
ASKER
Heck I turned off the firewall and still same issue so I'm thinking its not a firewall issue
windows 10 even when the windows firewall is off, i've seen the rules in still preventing ....
check the vpn adapter properties tcp/ip ipv4 properties, advanced, wins see which options you have default or netbiods over tcp/ip?
..
look at nbtstat as a way to see whether you receive netbios over tcp/ip events...
check the vpn adapter properties tcp/ip ipv4 properties, advanced, wins see which options you have default or netbiods over tcp/ip?
..
look at nbtstat as a way to see whether you receive netbios over tcp/ip events...
ASKER
thanks how do I look at nbtstat as a way to see whether you receive netbios over tcp/ip events?
nbtstat -c
to see if you received events
nbtstat -n
nbtstat -S
nbtstat -s
a long term solution is to setup a DNS server on the remote side that is passed when the VPN sets up.....
to see if you received events
nbtstat -n
nbtstat -S
nbtstat -s
a long term solution is to setup a DNS server on the remote side that is passed when the VPN sets up.....
ASKER
Can you elaborate on the nbstat commands - I don't know what I'm looking for as a result with each command you provided.
Thank you but still doesn't make sense... it was working then stopped. I don't think I want to setup a DNS server but rather find out why Windows stopped working the way it had been.
Thank you but still doesn't make sense... it was working then stopped. I don't think I want to setup a DNS server but rather find out why Windows stopped working the way it had been.
nbstat is a way to see whether it gets updates and lists nodes that it learned...
You have to determine what preceded the events when it stopped working.
An update? disabling SMB1 on the windows 7 and newer systems while the XP systems can not be updated as SMB1 is the only thing they know.......
You have to determine what preceded the events when it stopped working.
An update? disabling SMB1 on the windows 7 and newer systems while the XP systems can not be updated as SMB1 is the only thing they know.......
ASKER
When I enter nbtstat -c all I see if my computers IP address and a scope id of [ ] what does this mean?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
By default, Windows will append the DNS suffix to whatever computer name you put in to mimic NETBIOS, so you either have to make sure the DNS suffix being used by the client machine is the same as the destination computers. If it isn't, you have to use the whole DNS FQDN to connect (computer.domain.com is the FQDN of a computer with a name of COMPUTER).