01-06-2012 10:01 AM
I have recently "upgraded" to Uverse from SBC DSL. My new Uverse setup also has a wirless STB, so there is an additonal wireless box hooked up to the 2-Wire 3800 Gateway. This being said, the wireless STB uses port 443 to conduct its business. (I see that the 3800 has this port already forwarded to the wireless STB router). My WHS box also used that port for its secured logon.
I also incorporated my exisiting network (Netgear WNDR3700) behind the 2-Wire and everything works fine. I followed SomeJoe777's advice here: http://forums.att.com/t5/Residential-Gateway/U-verse-for-BUSINESS-2Wire-3600HGV-bridge-mode-or-anoth... I have the inside network in the 10.0.0 range and the 2-Wire remains in the 198.168.1 range, both on the 255.255.255.0 subnet.
I changed both the internet (port 80) and secured (port 443) to 1024 and 4443 respectively on my WHS IIS configuration. I did this following these instructions: http://www.myhomeserver.com/?page_id=23 I can access the WHS box fine using my domain name and my Internet IP address while inside the network. However, when I try to access the box from outside the network, I cannot get in. Does Uverse block those ports on the ISP side? SomeJoe777, are you out there? I've read a lot of your posts and look forward to your and anyone else's advice. Thanks.
Solved by: Go to Solution.
01-06-2012 11:12 AM - edited 01-06-2012 11:12 AM
Those ports (1024 and 4443) are not blocked by AT&T and should work for access to the WHS from the Internet. However, you will need to create a custom firewall rule for those ports on the 2Wire, and then apply that rule to the WHS. You cannot use the built-in rules for HTTP and HTTPS, since they would forward port 80 and 443, respectively.
01-06-2012 11:41 AM
01-06-2012 1:25 PM
01-06-2012 2:21 PM
Welcome to the internet boards! Check out our troubleshooting articles below and don’t forget to search the forums - your question may have been answered already!
Service acting up? Click here to troubleshoot now!
For DSL related issues. We highly recommend chatting with our teams to address this as quickly as possible.