One of my firewalls crashed last evening,
I had to run a bypass cable and reIP my PC, (ethernet)
now my PC has no internet connectivity
seems to not let me have access to the network
says "unknown Network" and "limited network connectivity"
how to I get this new network identified so my PC can get back online?
What's the IP address? Default gateway? Subnet mask? Do they match up with the VLAN that you're on?
And if it's 169.254.x.x, then your re-IP didn't work and it's got a default MSFT address.
Quote from: deanwebb on May 17, 2018, 10:17:17 AM
What's the IP address? Default gateway? Subnet mask? Do they match up with the VLAN that you're on?
And if it's 169.254.x.x, then your re-IP didn't work and it's got a default MSFT address.
no it's all good, the laptop does not get DHCP, from the DHCP server. it I set a static, everything works ok, (but that's not real portable)
did some research, came across a lot of other people with this issue, thing liek switching the device from public to private mode,
resetting the winsock, tcp stack, and interface. Falling short of deleting the wireless and reconfiguring which I don't really want to do
for now a static works. (and I will report that other devices on the network have no issue getting IP address from DHCP Server).
another odd thing, none of my vlan's behind the 3550 are working,
modem -> 3550 -? vlan 20
modem to 3550 on vlan10 172.16.1.0/28 172.16.1.1 on DSL modem 172.16.1.2 on vlan 10 on the 3550
vlan 20 svi 192.168.2.1 on 3550, my pc in vlan 20 192.168.2.2 GW 192.168.2.1 mask /24
have routes on the modem to push 192.168.2.0/24 to 172.16.1.2 on the 3550
I can ping my PC 192.168.2.2 from the DSL modem,
I cam ping the next hop isp ip from my PC 96.x.x.x
I get no DNS, and I can't browse via IP.
if I put PC in vlan 10 the 172.16.1.0/28 network all is well.
I ran a wireshark capture on my pc when trying to browse, all I get are DNS barfs, trying to resolve and cannot.
Basically, there are client settings on Windows that need to be worked with when messing with networks. Always check them when messing with networks.
There can also be stupid things to set up on ISP gear... does the ISP gear filter out traffic that's not on the 10.0.0.0/8 network?
Quote from: deanwebb on May 18, 2018, 12:28:27 PM
Basically, there are client settings on Windows that need to be worked with when messing with networks. Always check them when messing with networks.
There can also be stupid things to set up on ISP gear... does the ISP gear filter out traffic that's not on the 10.0.0.0/8 network?
PAT is configured, possible it doesn't PAT for other than that 172.16.1.0/28 network. possible because I (may have double PATd with my linksys firewall that died, it may have PAT'd everything to the FW outside interface, then the DSL modem thought everything was coming in from a 172.16.1.2 IP, ( what used to be my firewall outside interface) that would make sense.
Yeah, that home gear gets easily confused. If you do the PAT before it hits the ISP router, then it should have no issue getting out.