F5F Stay Refreshed Power Users Networks Windows Network IP issue

Windows Network IP issue

Windows Network IP issue

G
gadval03
Junior Member
6
12-30-2023, 01:22 AM
#1
I'm facing problems connecting via computer names. I've been trying for a while but haven't found a fix. Did you try using NSlookup to discover the IP? For example, if PC 1 is what you need, nslookup showed it as Computer1 IP 192.168.1.25. The DHCP listed the PC name with IP 192.168.0.10, which worked. I can log in there. What could be wrong with the computer name login? I also ran another NSlookup for 192.168.1.10 and got a phone number instead of an IP—seems incorrect. Any clues on what's going wrong or how to resolve it? It seems everything works with Windows Active Directory.
G
gadval03
12-30-2023, 01:22 AM #1

I'm facing problems connecting via computer names. I've been trying for a while but haven't found a fix. Did you try using NSlookup to discover the IP? For example, if PC 1 is what you need, nslookup showed it as Computer1 IP 192.168.1.25. The DHCP listed the PC name with IP 192.168.0.10, which worked. I can log in there. What could be wrong with the computer name login? I also ran another NSlookup for 192.168.1.10 and got a phone number instead of an IP—seems incorrect. Any clues on what's going wrong or how to resolve it? It seems everything works with Windows Active Directory.

J
JRiley
Member
114
01-09-2024, 02:36 PM
#2
Instead of struggling with this method, you might want to try a program like VNC Viewer. There are tools you can install on both the host and the remote client. I only suggest using it within a private network. It lets you give names to your network devices and connect without entering IP addresses. However, if you follow these steps carefully, assigning static IPs to each machine is essential. If their IP changes, VNC Viewer will stop working properly.
J
JRiley
01-09-2024, 02:36 PM #2

Instead of struggling with this method, you might want to try a program like VNC Viewer. There are tools you can install on both the host and the remote client. I only suggest using it within a private network. It lets you give names to your network devices and connect without entering IP addresses. However, if you follow these steps carefully, assigning static IPs to each machine is essential. If their IP changes, VNC Viewer will stop working properly.

L
liang_hao_yan
Member
221
01-14-2024, 06:30 PM
#3
Choose between TeamViewer and VNC for remote access.
L
liang_hao_yan
01-14-2024, 06:30 PM #3

Choose between TeamViewer and VNC for remote access.

J
JeronimoYT
Senior Member
428
01-15-2024, 02:01 AM
#4
VNC is sending a signal, but I’m puzzled about why it’s happening now. Maybe DNS is involved?
J
JeronimoYT
01-15-2024, 02:01 AM #4

VNC is sending a signal, but I’m puzzled about why it’s happening now. Maybe DNS is involved?

S
Swift724
Junior Member
45
01-15-2024, 10:23 PM
#5
The PCs in the active directory DHCP should display the clock icon instead of the pen active lease and DNS dynamic update pending. The requested address isn't available for lease through the DHCP server. I couldn't find a solution on Google, though—I've released the IP using ipconfig /release.
S
Swift724
01-15-2024, 10:23 PM #5

The PCs in the active directory DHCP should display the clock icon instead of the pen active lease and DNS dynamic update pending. The requested address isn't available for lease through the DHCP server. I couldn't find a solution on Google, though—I've released the IP using ipconfig /release.

F
floundershy
Member
191
01-28-2024, 09:04 PM
#6
You might adjust the configuration so the DHCP server updates the DNS independently, rather than depending on the client.
F
floundershy
01-28-2024, 09:04 PM #6

You might adjust the configuration so the DHCP server updates the DNS independently, rather than depending on the client.