Comments
-
@shaazaminator I want to thank you your insight and comments about 3cx phones. To answer some of your questions: Our phones and Pc's are not on the same subnet. Pc's are on a separate trusted network VLAN1-10.xxx.xxx.xxx; Phones are on Optional network VLAN50-xxx.xxx.50.100 - .199 Yes, the network cable runs to the phone…
-
@Bruce_Briggs and @"james.carson" I did open a case with Watchguard; #02078563, which has been closed. Worked mostly with Ryan in trying different things, he had me looking over my network for potential problems. I could not find anything new or any changes that might have occurred due to the power outage. We didn't come…
-
Thanks Bruce, I opened a case with WG, I'll update when we have an answer. I also bumped up my DHCP diagnostic logs to med. Probably with the idea I was going to be upgrading, higher version of WSM when upgrading FSM and now I'm way behind. Next on my list, update my Firebox!!
-
@"james.carson" Thank you for your responses, I appreciate the insights.
-
Thanks Bruce! I couldn't see any way of doing it but I had to make sure and ask. I have multiple VLANs they need to test and I have one that just won't run to completion. My logs don't show any failed / denied connections and their suggestion was the whitelisted MAC. I'm going to compare my logs of the failed tests to a…
-
@Bruce_Briggs Thank you for the links. That worked perfectly.
-
Yes, I have one confirmed tested and working.
-
@Bruce_Briggs Thanks for the information, as usual, very helpful! I went brain dead, too many things going on; "Pc won't get tagged packets", I forgot! I had to change my Interface 2 to "send and receive untagged traffic for VLAN 70 and turn off (uncheck) the "send and receive tagged traffic for selected VLAN" (no VLAN…
-
From what I understand, the AuthPoint user name has to be the exact same as the Pc user name, correct?
-
Support didn't have any answers at this time since it's not acting up at this time. All I can think of is the time frame that I power cycled the AP after the hard reset after I had taken it down. I thought I did that same process while it was still mounted to the ceiling but I might have waited longer (too long) after the…
-
@DStone Yes, the AP's that were going "not trusted" were setup as DHCP. Support suggested I change those AP's to static IP's or with a reserved IP, which I did. It's been 11 days now since I have made that change and non of them have gone "not trusted". A simple config change which I didn't catch to fix the problem.
-
@James_Carson I opened a case for these 'not trusted' #01576944
-
@James_Carson I opened a case for the failed upgrade #01576953
-
I reset the AP325 once again and here are the logs whiles it's going through it's steps: unreachable > not trusted > mark trusted > updating configuration > discovered > updating configuration > unreachable 2021-09-10 10:34:37 Allow 172.16.10.10 172.16.10.104 icmp Firebox Mngmnt Allowed 48 64 (Any From Firebox-00)…
-
I reset the AP325 once again and here are the logs whiles it's going through it's steps: unreachable > not trusted > mark trusted > updating configuration > discovered > updating configuration > unreachable 2021-09-10 10:34:37 Allow 172.16.10.10 172.16.10.104 icmp Firebox Mngmnt Allowed 48 64 (Any From Firebox-00)…
-
I reset the AP325 once again and here are the logs whiles it's going through it's steps: unreachable > not trusted > mark trusted > updating configuration > discovered > updating configuration > unreachable 2021-09-10 10:34:37 Allow 172.16.10.10 172.16.10.104 icmp Firebox Mngmnt Allowed 48 64 (Any From Firebox-00)…
-
I reset the AP325 once again and here are the logs whiles it's going through it's steps: unreachable > not trusted > mark trusted > updating configuration > discovered > updating configuration > unreachable 2021-09-10 10:34:37 Allow 172.16.10.10 172.16.10.104 icmp Firebox Mngmnt Allowed 48 64 (Any From Firebox-00)…
-
James_Carson; thank you for the response. That was probably going to be my next step besides trying different FW versions to see If I could narrow it down. But I'm also thinking I could be chasing my tail by doing so. I'll post what I find out.
-
I reset the AP325 once again and here are the logs whiles it's going through it's steps: unreachable > not trusted > mark trusted > updating configuration > discovered > updating configuration > unreachable 2021-09-10 10:34:37 Allow 172.16.10.10 172.16.10.104 icmp Firebox Mngmnt Allowed 48 64 (Any From Firebox-00)…
-
While trying to fix this issue I upgraded two of my AP325's to a newer FW. I updated one from 8.5.0-658 to 8.8.3-12 without any problems. I went to update another AP325 from 8.5.0-658 to 8.8.3-112 and it won't update or I should say it appears to update but it shows "unreachable". I removed the AP and tried to reinstall it…
-
Being late to the discussion; this apparently isn't a new issue and it's still an issue with more current firmware/fireware. This past year we upgraded from 2-XTM 515's to a M370 while adding several more AP's. I've been noticing that on a semi regular basis our AP's go "not trusted". It also is random as far as which ones…
-
Bruce, Thanks for the reply and added insight as always. Somewhere between answering your first comment and now, the website is working ok. I'm going to assume somewhere out on the internet there was a network issue. It didn't make sense why my test Pc connected directly to my comcast modem got to the website and my…
-
from a desktop that goes through our firebox and a http policy. a test pc I have that 'doesn't' go through our firebox does access our website.
-
A late update: everything is working at this time. AP125 v8.6.0-644.3 is showing me SSID's and connected clients AP325 v8.5.0-658 is showing me SSID's and connected clients
-
Thanks Bruce, I just wanted to be reassured I wasn't going to break something I wasn't thinking of.
-
Good Morning @Bruce_Briggs Thank you, I downgraded two so far (8.5.0-658) and I'm seeing who's connected. I'll have to work my way back up to see which one breaks the list.
-
Update; I fixed / updated my Dimension this weekend. (Server went sideways a couple of weeks ago and I couldn't log in). Now that I could see my log history again, I noticed that the CC machines weren't being listed/seen in either firewall!?? So, by chance I filtered by the 'old' IP address of the CC machine. Low and…
-
Update! I updated most of my AP's this weekend to the latest firmware for each. What I've noticed so far is this; The latest firmware 8.9.0-63 will show I have clients connected in GWC but when I click "Wireless Clients" to see who's connected and which SSID they're using the AP's with the firmware 8.9.0-63 aren't listed.…
-
@Bruce_Briggs Thank you for your input. I did reboot a couple of the CC machines but not for the reasons you suggest. I thought maybe they needed a reboot to save the changes properly. After hours I did go to all my network switches and both firewalls and shut them down / reboot them, hoping to clear out any left over ARP…
-
@Bruce_Briggs The DNS messages were from a misconfiguration in the Phone Switch(system). They finally went in and made some changes! The "getting the wrong IP" was a network (cisco) switch configuration issue. I needed to turn on LLDP for each switch and config. the ports for Voice VLANs with my Voice VLANID. Your help is…