Windows update
-
I added a rule just like the lan one but it still not letting me get my windows update i still get the error that it isn't talking to the update server at Microsoft.
-
Did you setup any IPv6 on your pfSense?
I am just thinking that maybe if the WiFi interface has been given an IPv6 address, and the Windows devices learn an IPv6 address that looks global… then they will think that IPv6 is available and try to use the Windows Update server at its IPv6 address.Do```
ipconfigThis is just a stab-in-the-dark from me - I thought of it when I noticed that the default pass all rule for IPv6 is not there on LAN.
-
No sir i don't have any of the IPv6 address stuff set up as far as i know all the ipv6 stuff is turned off. I only run ipv4 as far as i know. is there a file or log or something you could look at that might tell you where I am, going wrong with my setup maybe.
-
Not only am I not able to get my windows updates still I cant get the Pandora or instagram to work on this thing all on the wireless side can someone please tell me where to go to fix this and what info you need to help me. I just don't get it build this thing to help protect my systems and now it wont even let me do anything with the windows updates and the Pandora and the instagram on the wireless side of the system.
-
You cannot install Windows updates on Ubuntu ;D
-
i am not trying to install on Ubuntu thats just the system i used to show the screen shots of the firewall rules that is just one of my 10 systems that are on the wired side the netbook and a kodi rig are my only two windows based systems the kodi system is wired and the netbook is on the wireless side along with my two phones.
The wired side seems to work ok its the wireless side that wont download the windows updates. keeps giving me the error that i need to add the Microsoft web address to the firewall exceptions or allow list and i must be stupid cause i don't know where to find such a place in the pf sense firewall stuff i love this thing but i don't understand where i am suppose to put such things. just a little help would be greatly appreciated.
-
I was in the mood for a some unseriousness ::)
Do you have name resolution on your wifi interface, e.g. can you browse or ping update.microsoft.com from those machines not working properly?
With that much problems there seems to be missing something basically.
Which version of pfSense are you running? -
Mr jahonix:
No i can not ping update.Microsoft.com from my netbook But it works on my wired windows system just fine its just my three wireless systems that are not talking to the programs i have listed in the last few post.
i did an Microsoft windows update on my desktop Wired windows system and it went through just fine but i can not get the wireless netbook to update it keeps telling me the same error as reported in the one post so i am at a total loss why the wireless side is goofing up and the wired side is not.
Just not sure what i am missing here
Version 2.3.4-RELEASE (i386)
built on Wed May 03 15:22:11 CDT 2017
FreeBSD 10.3-RELEASE-p19 -
Which error do you get when trying to ping www.google.com or anything not local?
You either have no DNS server configured for that interface or you're missing rules.
-
How about a screenshot of your Outbound NAT entries. Also, try pinging 4.2.2.2 from the WLANWIFI network.
-
This is my out bound Nat settings & for the pinging of 4.2.2.2 worked ok so did ping google.com But ping of update.microsoft.com still not working. This is the ping from the wlanwifi side from my net book it says4 sent and 4 received for the google & 4.2.2.2 but for the microsoft update it says request timed out twice 2 sent 2 lost
The two screen shoots are of the same thing just one is the top of the page and the other is the rest of the page
Thanks for all your help this far i just want to say I thought I knew what i was doing but i guess i am not as smart as i thought i was.
is there any more files or areas you folks may need to look at i can set up my teamviewer so someone can log in and look at the whole setup and maybe be able to fix it them selfs i am more than happy to do that thanks again. Wildmanron



 -
Do a tracert to update.microsoft.com and see the hops it goes along.
tracert update.microsoft.com
That will tell you if it ever leaves the firewall towards the internet, or is spinning around or dropped somehow in pfSense or your own network.
-
Ok i thank you for this command but can you explane to me how to use the command and witch one of the systems do i use to issue the command from.
-
From one of the Windows systems on the WiFi, and do it from a Windows System on the wired LAN also. Then you can compare the output and see what is different about the way the network is routing.
-
Heres what it says for the Wifi side top picture bottom is the wired side


-
Strange, before I posted to ping update.microsoft.com I checked and could ping it. Now it times out here as well.
Your trace routes clearly show that your router is working. The Microsoft Network (msn.com) is having problems getting your packets to its destination. Nothing you can do about that.
-
Ok i Thank you for this info. Ok so what about the wireless side of the cell phone trouble with the Pandora & Instagram also i just did another update on my wired Windows desktop and it went through just fine but the wireless netbook is still not updating.
-
Both of those trace route commands are having trouble getting to update.microsoft.com - so that does not really help us to know what is the difference between your wired LAN and your WiFi.
If you know the places where Pandora and Instagram go on the internet to "do their thing", then try tracert to those places.
The aim is to find some difference between wired and WiFi routing or packet filtering that will then give a clue where to look (pfSense settings, modem to ISP or…?)
-
Ok here is the trace routes to pandora and instagram instagram dose the same as microsoft but pandora goes through
I am sorry for the side ways pictures for some reason they keep turning all different way but the way i want them when i upload them to you folks so i am sorry i don't know what to do to change that on my end
these are all done on the wireless side
-
They are all routing out to the internet. The various "timed out" once it gets ot to the internet are to be expected. Not all router ops along the way are going to respond to ping/tracert. But the fact that you get various responses back from out on the real internet means that the packets are passing through pfSense and the routing and NAT are working.
Have you moved a system from WiFi over to wired and confirmed that it works, just by switching off its WiFi and plugging in a cable?