LAN client cannot connect
-
@stephenw10 i have only status / DHCPv6
maybe is writing status / release DHCP??
-
Ok maybe you disabled IPv4 DHCP when you change the LAN IP.
Go to Services > DHCP Server > LAN and make sure it's enabled.
-
@stephenw10
Services > DHCP Server > LAN
Enable - Enable DHCP server on the LAN interface (yes)
Is this feature already enabled or is it something else I need to look at? -
Yes it should be enabled by default. Check Status > Services.
-
@stephenw10 status/service
service
dhcpd service DHCP
dpinger Demon Monitoring Gateway
ntpd NTP Time Synchronization
syslogd System registry daemon
unbound DNS Resolver -
Hmm, seems very odd that there's no DHCL leases shown. I don't think I've ever seen that.
What IP address is your Windows client using?
Did you set that statically? If not it must have pulled it via DHCP.
-
@stephenw10 said in Hardware driver:
What IP address is your Windows client using?
Did you set that statically?
goodmorning. how i see this? windows - cmd - ipconfig?
-
Yes
ipconfig /allshould show it. Though it's been years since I ran Windows! -
@stephenw10 ok,
connection-specific dns suffix: brokenboy.local
dhcp enabled: yes
automatic configuration enabled: yes
ipv5 address local to the link: xxxxxx (preferred)
ipv4 address: 192.168.100.xx(preferred)
lease obtained at 10 am
lease scanned at 5pm
default gateway, dhcp server, dns server are the same 192.168.100.xlan cards, local network connection are disconnected (obviously, because the pc is not connected to the switch)
-
Ok that's good.
I assume the client still cannot resolve wikipedia.org?
Go to Diag > DNS Lookup in pfSense and check wikipedia.org there. Make sure all defined DNS servers are able to resolve it.
Steve
-
@stephenw10 DNS Lookup
Hostname
wikipedia.org
Results
Results Record type
185.15.58.224 A
2a02:ec80:600:ed1a::1 AAAA
Timing
Name server Time of request
127.0.0.x 45 msec
192.168.1.xxx 15 msec
1.1.1.1 2 msec
8.8.8.8 2 msec
More information
Ping
Traceroute -
Hmm, that all looks good then. Is the client still unable to resolve it?
-
@stephenw10 Is not yet able.
-
pfSense is showing that localhost (127.0.0.1) can resolve it. That's the local DNS resolver, Unbound.
LAN side clients should be using that to resolve against. The fact your client cannot implies it isn't using pfSense.
Can you test with a different client?
-
@stephenw10 how? can you explain in less technical words please? imagine that i am 12 years old, please
-
S stephenw10 moved this topic from Hardware on
-
I forked this topic since this is not an issue with the driver.
Either test using a different client if you can.
Or test from Windows using the IP address of the LAN IP directly like:
nslookup wikipedia.org 192.168.100.1