F5F Stay Refreshed Hardware Desktop Unable to connect to a particular device via the network.

Unable to connect to a particular device via the network.

Unable to connect to a particular device via the network.

Z
zmanrules987
Member
218
06-03-2023, 01:57 AM
#1
Hi, I see you're dealing with network access issues. It sounds like you're having trouble connecting to your PC over the network. Have you tried checking the IP settings or ensuring the correct network path is selected? Also, verify that the remote tool is configured properly and that the PC's IP is correctly shared. Let me know if you need further guidance!
Z
zmanrules987
06-03-2023, 01:57 AM #1

Hi, I see you're dealing with network access issues. It sounds like you're having trouble connecting to your PC over the network. Have you tried checking the IP settings or ensuring the correct network path is selected? Also, verify that the remote tool is configured properly and that the PC's IP is correctly shared. Let me know if you need further guidance!

R
Recilon
Junior Member
23
06-03-2023, 02:42 AM
#2
We're discussing various operating systems, potential firewall configurations, and network connectivity. It seems there may be issues with network segmentation—machines pingable from one but not another suggests separate subnets or routing problems. I'm assuming DHCP is providing IP addresses, but inconsistent access points point to possible misconfigurations or isolated networks.
R
Recilon
06-03-2023, 02:42 AM #2

We're discussing various operating systems, potential firewall configurations, and network connectivity. It seems there may be issues with network segmentation—machines pingable from one but not another suggests separate subnets or routing problems. I'm assuming DHCP is providing IP addresses, but inconsistent access points point to possible misconfigurations or isolated networks.

S
Sophsta
Member
164
06-04-2023, 11:18 AM
#3
I question if the operating system issue lies in the fact that different Windows versions (7, 8.1, 10) can reach the machine I can't. The IP range and VLAN aren't the cause because other VLANs can still connect to tools like TightVNC, network sharing, and ping attempts I'm unable to make. The main issue is on the device I use. I was able to reach it before yesterday, but not until yesterday I encountered this problem. For instance, Windows 10 with ESET Antivirus using IP 10.44.0.124 can connect through a Fortinet firewall, while another Windows 8.1 with the same antivirus and IP can also access it. A third setup with IPs 10.44.8.11, 10.44.8.59, and 10.44.8.24 works fine for some connections. However, PCs that can reach the first IP (10.44.10.246) still can't access the problematic Windows 10 instance. I've tried Checkdisk, Sfc scannow, and system restore, but nothing resolves it.
S
Sophsta
06-04-2023, 11:18 AM #3

I question if the operating system issue lies in the fact that different Windows versions (7, 8.1, 10) can reach the machine I can't. The IP range and VLAN aren't the cause because other VLANs can still connect to tools like TightVNC, network sharing, and ping attempts I'm unable to make. The main issue is on the device I use. I was able to reach it before yesterday, but not until yesterday I encountered this problem. For instance, Windows 10 with ESET Antivirus using IP 10.44.0.124 can connect through a Fortinet firewall, while another Windows 8.1 with the same antivirus and IP can also access it. A third setup with IPs 10.44.8.11, 10.44.8.59, and 10.44.8.24 works fine for some connections. However, PCs that can reach the first IP (10.44.10.246) still can't access the problematic Windows 10 instance. I've tried Checkdisk, Sfc scannow, and system restore, but nothing resolves it.