No internet access, but webgui works

itsignas

No, it's DNS issue. Your PC LAN rule should use * for protocol, not just IPv4 TCP, but that's not your issue. Your issue is purely DNS-related since you can access websites based on their IP address but not FQDN. Your Windows XP client that was missing DNS details, what did you do about that? I had recommended several DNS servers that you could use, and you replied that it didn't work and I then asked what exactly did you do.

Okay so yea, what I did i set it to GET DNS AUTOMATICALLY, same settings for other LAN (OPT1, which works without problems).

ESXI have it own settings for management console (Maybe interrupting DNS with pfsense?) (photos included)
http://imgur.com/a/2AQ4b

KOM

Humour me and set it manual DNS, 8.8.8.8 and then try again.

itsignas

@KOM:

Humour me and set it manual DNS, 8.8.8.8 and then try again.

Esxi or client?

KOM

Client. ESXi isn't making the DNS calls on behalf of the VM, the VM is, so we only care about setting client DNS.

itsignas

@KOM:

Client. ESXi isn't making the DNS calls on behalf of the VM, the VM is, so we only care about setting client DNS.

http://prntscr.com/aarmyu
Same result

KOM

Since we have already confirmed that you can go places based on the IP address, it's definitely a DNS problem. However, use of manual DNS seems to fail. Is it possible your ISP is blocking the use of external DNS servers? In pfSense, what do you have for System - General Setup - DNS Servers?

itsignas

@KOM:

Since we have already confirmed that you can go places based on the IP address, it's definitely a DNS problem. However, use of manual DNS seems to fail. Is it possible your ISP is blocking the use of external DNS servers? In pfSense, what do you have for System - General Setup - DNS Servers?

http://prntscr.com/aarycx
http://prntscr.com/aaryi4
http://prntscr.com/aaryo9

Here you go

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.

itsignas

@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 :/

7kJ6k4k.png_thumb

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?

itsignas

@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)

11111111111.png_thumb

222222222.png_thumb

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?

itsignas

@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.

![dns resolver general settings.png](/public/imported_attachments/1/dns resolver general settings.png)
![dns resolver general settings.png_thumb](/public/imported_attachments/1/dns resolver general settings.png_thumb)
![dns forwarder off.png](/public/imported_attachments/1/dns forwarder off.png)
![dns forwarder off.png_thumb](/public/imported_attachments/1/dns forwarder off.png_thumb)

KOM

OK, run nslookup again and this time type server 192.168.3.1 then try to resolve youtube.com. What happens?

itsignas

@KOM:

OK, run nslookup again and this time type server 192.168.3.1 then try to resolve youtube.com. What happens?

Here

Screenshot_2.png_thumb

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)?

itsignas

@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

Screenshot_1.png_thumb

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.

itsignas

@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?

Screenshot_1.png_thumb

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.