![]() Lastly, it is running online backups with I-Drive. This machine is also the primary ACT database server, so this application will spawn several SQL server links. It is the primary shared network server with the all the PCs having several files open at any time. The server otherwise seems to be running OK. ![]() I am not entirely sure what to make of it. They pointed at the listing below from the firewall log (excerpt below, more in attached txt file). As say, why do I make rules if not being followed.Had a problem with a hosted VoIP phone system at a site today, and the hosted provider suggested that the problem was due to excessive DNS connections from domain controller. This scratches my head, what attempt to go around my settings? It not get around, but it my settings, and not do I like that auto-dns program that pays not to my own rules. If not else is running but the chrome, what else can be? May haps that I turn off dns service, but that not cacheing. This not even use packet sniff yet, so not telling yet, but think it can be chrome. Only see for people to know how to use the 8.8.8.8:53, not even to block it or why it shows head to me. So question is, what can cause this? is chrome having option to use google dns somehow? I not see that answer when looking on the internets. Packets I see now are to 8.8.8.8:53, but rejected. ![]() No funny stuff, is as should be.įirewall rules in pfsense state to say for all lan ip, when packet upd or tcp go to port 53, reject if not to norton dns. Machine then use router to get dns, whether static or given dhcp. Now as the router is giving out ip (or can static it too) it must be one ip I assign. This does the keeping of unknown peoples out and makes me only allow those machine that are ok by me. each client thenfor has MAC address to know. options to deny unknown client is on, so only those that are in reserved dhcp list are being able to get on. dhcp server is giving ip to machine, even if machine is static, but if not is served. ![]() for settings, if coding static ip to 192.168.1.100 wit subnetting at 255.255.255.0 that gateway be is of course the router of 192.168.1.1. Yes, 8.8.8.8 is dns, as port 53 does tell.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |