jmair Posted January 13, 2014 Posted January 13, 2014 How many times have we read/heard that issue. It sounds funny to post that as a subject but that's what it comes down to really. I have an ip that won't go past our gateway and we have no reason to believe it's the gateway (a port on our firewall) that's stopping it. 10.1.10.10 on any machine will not access beyond our network. It can ping external IPs, but looks to have no DNS issues. Once I swap the IP to 10.1.10.9 (just one off) and everything works like a charm. When the ip is 10.1.10.10 I can access any/all on our lan seemingly just fine. I have checked our DHCP and confirmed the ip is no on a DENY list and I've made sure that we don't have a conflicting IP and the event logs show nothing (no DNS issues, networking or IPv4 issues). When I call support, that handles our firewall, they can't find any rule that would block this particular IP and they believe it's on my side. Any suggestions on where to look or what commands I can run to help figure out what would be causing this problem? ((this has been going on for 3 weeks now)) Thank you kindly.
Michael Posted January 13, 2014 Posted January 13, 2014 When you set the workstation to 10.1.10.9 can you ping 10.1.10.10 successfully?
jmair Posted January 13, 2014 Author Posted January 13, 2014 When you set the workstation to 10.1.10.9 can you ping 10.1.10.10 successfully? Yes, both direction just fine.
Michael Posted January 13, 2014 Posted January 13, 2014 Well if you can ping 10.1.10.10 when your workstation is set as 10.1.10.9, it means something's using 10.1.10.10.
jmair Posted January 13, 2014 Author Posted January 13, 2014 I see what you were trying to deduct. I thought you were trying to see if client to client could ping each-other on the lan side. No, their is no IP conflict (I wish their was, it would have been an easy fix).
jmair Posted January 15, 2014 Author Posted January 15, 2014 {SOLVED} The firewall Octet range wasn't encompassing the entire lan scope. Online IP Subnet Calculator for the win! 1
mac_shinobi Posted January 15, 2014 Posted January 15, 2014 {SOLVED} The firewall Octet range wasn't encompassing the entire lan scope. Online IP Subnet Calculator for the win! What did you have to do on your firewall to update / resolve that issue ?
jmair Posted January 15, 2014 Author Posted January 15, 2014 First I have to say that the PaloAlto firewalls are slick very powerful firewalls. I'm sure all current generation firewalls are. But they are far more complicated to manage than one just 5 years ago. Days of logging in and looking at two tabs or running a few commands are long gone. We have a port configured as our gateway. It was configured as 10.1.1.254/21 .. Changing it to 10.1.1.254/20 , routing was solved. 10.1.1.254/21 took it to 10.1.7.254 and changing it to 10.1.1.254/21 took it up to 10.1.15.254 witch encompassed the 10.1.10.10 ip. Not sure why the 10.1.10.9 worked though, I'll chalk it up to an adventure I get to figure out at a later time. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now