A user on our corporate network is trying to connect to an SSL website that refuses to work. I can connect to it from my home computer, and I can connect to it if I plug directly into the modem (and get a public IP), but once I go behind our Linksys WRT54G, I can no longer connect to the site. Other normal SSL websites work, just not this one.
Its a simple linksys router, and I've never dealt with this website so theres no way its been blocked manually on the router. I'm using the same router at home and the site works fine. The one difference is at work we're using a less popular internal IP (NAT) as in 172.25.200.x, where as at home, the computer is 192.168.1.x. Is it possible that their firewall is blocking connections from a different NAT IP ranges? I'm guessing the internal (NAT) IP's are bundled inside the packet, so a SPI box on the other end could refuse the connection.
Any ideas on whats going on?
Its a simple linksys router, and I've never dealt with this website so theres no way its been blocked manually on the router. I'm using the same router at home and the site works fine. The one difference is at work we're using a less popular internal IP (NAT) as in 172.25.200.x, where as at home, the computer is 192.168.1.x. Is it possible that their firewall is blocking connections from a different NAT IP ranges? I'm guessing the internal (NAT) IP's are bundled inside the packet, so a SPI box on the other end could refuse the connection.
Any ideas on whats going on?