No internet access, but webgui works
-
@KOM:
Next test: on your client, set DNS manually to 212.59.8.8 and try again. BTW you can embed images directly into your posts here without having to upload them to some 3rd-party site and then link to them.
Same :/
-
So bizarre. Try this. On your XP client, run a Command Prompt. Type nslookup and press enter. Type server 212.59.8.8 and press enter. Type youtube.com and press enter. What happens? When I try it here, your 212.59.8.8 DNS server times out, but that might be because I'm not on their network. Does it time out for you too? If so, type server 8.8.8.8 and press enter. Type youtube.com and press enter. What happens?
-
@KOM:
So bizarre. Try this. On your XP client, run a Command Prompt. Type nslookup and press enter. Type server 212.59.8.8 and press enter. Type youtube.com and press enter. What happens? When I try it here, your 212.59.8.8 DNS server times out, but that might be because I'm not on their network. Does it time out for you too? If so, type server 8.8.8.8 and press enter. Type youtube.com and press enter. What happens?
Mhmm. That's weird. Attaching photos.
Second is from my other lan (OPT1)
-
OK now we're getting somewhere. The one that work sis using pfSense as its DNS. In pfSense, are you using the Forwarder or Resolver? Look under Services at each one and see which one is enabled. For the one that's enabled, what do you have set for Networks Interfaces / Interfaces?
-
@KOM:
OK now we're getting somewhere. The one that work sis using pfSense as its DNS. In pfSense, are you using the Forwarder or Resolver? Look under Services at each one and see which one is enabled. For the one that's enabled, what do you have set for Networks Interfaces / Interfaces?
Here it is.
 -
OK, run nslookup again and this time type server 192.168.3.1 then try to resolve youtube.com. What happens?
-
@KOM:
OK, run nslookup again and this time type server 192.168.3.1 then try to resolve youtube.com. What happens?
Here
-
OK. I'm not sure why your pfSense LAN IP is 192.168.1.1, but you can resolve hosts via 192.168.1.254. Can you take a new screen of your pfSense console view (the one that lists the NICs and the menu showing options form 0 to 15)?
-
@KOM:
OK. I'm not sure why your pfSense LAN IP is 192.168.1.1, but you can resolve hosts via 192.168.1.254. Can you take a new screen of your pfSense console view (the one that lists the NICs and the menu showing options form 0 to 15)?
Alright
-
My mistake, you weren't resolving use 192.168.1.254. Your OPT1 link was resolving using 212.59.8.8. So why can't LAN resolve using the same DNS server? I'm starting to run out of ideas here. It should just work.
-
@KOM:
My mistake, you weren't resolving use 192.168.1.254. Your OPT1 link was resolving using 212.59.8.8. So why can't LAN resolve using the same DNS server? I'm starting to run out of ideas here. It should just work.
That's the problem. Im just thinking that esxi is overriding dns server?
-
No, that has nothing to do with it. Usually, your public link to your ISP is a 100 Mbit connection , and LAN connections are Gigabit. In your case though, your public is Gigabit and LAN is 100 Mbit. I'm wondering if you have your vSwitches defined incorrectly. Pull the plug on your cable to your ISP and then check which interface in vi-client shows as being disconnected.
-
@KOM:
No, that has nothing to do with it. Usually, your public link to your ISP is a 100 Mbit connection , and LAN connections are Gigabit. In your case though, your public is Gigabit and LAN is 100 Mbit. I'm wondering if you have your vSwitches defined incorrectly. Pull the plug on your cable to your ISP and then check which interface in vi-client shows as being disconnected.
Well yes, my win xp machine is netbook, so it have only 100mbit connection, don't support gigabit.
-
I'm talking about your ESXi host. ESXi seems to have Gigabit to your ISP and OPT1, but 100 Mbit to LAN. That is unusual. You don't have your XP laptop connected directly into the ESXi host, do you? It should be plugged into a switch that is also plugged into ESXi, unless you're using a crossover cable.
-
@KOM:
I'm talking about your ESXi host. ESXi seems to have Gigabit to your ISP and OPT1, but 100 Mbit to LAN. That is unusual. You don't have your XP laptop connected directly into the ESXi host, do you? It should be plugged into a switch that is also plugged into ESXi, unless you're using a crossover cable.
Actually I do…
OPT1 goes to my switch which is connected to the my pc, which works okay.
But LAN doesn't as we trying to figure it out few hours now..jpg)
.jpg_thumb) -
I'm getting confused. Your XP PC was on LAN, I thought, since that is the one that can't resolve IP addresses. Maybe you could draw me a simple network diagram to show what is connected where?
-
@KOM:
I'm getting confused. Your XP PC was on LAN, I thought, since that is the one that can't resolve IP addresses. Maybe you could draw me a simple network diagram to show what is connected where?
Okay, im not great at these things, i'll attach photo too.
-
If I'm understanding this diagram, you have your WinXP box plugged directly into your ESXi hosts's network port? That won't work.
-
@KOM:
If I'm understanding this diagram, you have your WinXP box plugged directly into your ESXi hosts's network port? That won't work.
Well, but I can access esxi management and pfSense from it. That problem with dns, that we are having here
-
Unless the cable you're using is a crossover cable, it shouldn't work at all and I don't understand why it's working as much as it is. Do you have access to another switch or hub that you could put between ESXi and WinXP? Otherwise I'm out of ideas.
