loudog1327
join:2009-11-06
Wheaton, IL
| 2701-HG B Public IP issue.
Hello, so here is a quick rundown of my setup. I have a server that was freshly installed with server 2008, it has a dual port nic. I just installed this 2701-HG B and got everything connected and all the devices can access the internet just fine. I also have a bank of 5 static IP's.
To configure the public IP for the server I did the following.
1. Enabled the "Public Routed Subinterface"
2. Gave it the first of my 5 static ip addresses x.x.x.24
3. The subnet att gave me 255.255.255.248 is not a valid subnet for this IP so I used 255.255.0.0 and the router took that just fine.
4. I went to the address allocation table and found the server NIC that I want to use for my external connection. I then disabled the firewall on this connection and told it to use a public IP, from the dropdown I then selected the next IP in the range ATT had provided x.x.x.25
5. The router then stated to renew DHCP which I did and now the server's external nic gets the ip of x.x.x.25.
I cannot ping this nic in the server from an outside connection. Could ATT have given me incorrect information in terms of my static IP bank? Or did I configure something wrong in setting up the public IP? Any ideas? |
|
muiredised
ESSE QUAM VIDERI
join:2007-06-11
Tacoma, WA
| said by loudog1327  :3. The subnet att gave me 255.255.255.248 is not a valid subnet for this IP so I used 255.255.0.0 and the router took that just fine... ...Or did I configure something wrong in setting up the public IP? Any ideas? Hmmm. You asked for ideas, try setting up with the information provided by the ISP. The subnet they provided you works in their "sticky static" scheme. 2wire used to call this feature "Public Proxied Subnet/Nat routed".
A second idea, did you uncheck the box that enables firewall protection when you allocated the addy?
--
Assiduus usus uni rei deditus et ingenium et artem saepe vincit |
|
loudog1327
join:2009-11-06
Wheaton, IL
| Well I cannot control what IP address is the start point under "Public Proxied Subnet/Nat Routed" There is no way for me to edit the address there and the address displayed is not in the range of my static IP's. And yes I did disable the firewall protection when allocating the address. |
|
loudog1327
join:2009-11-06
Wheaton, IL | I have also been working through the ATT forums as well and it appears I may have mad a mistake in my IP address scheme. I believe that I may have given a reserved address in place of my first static IP. Which would make sense for my problem. |
|
muiredised
ESSE QUAM VIDERI
join:2007-06-11
Tacoma, WA
| reply to loudog1327
said by loudog1327 :Well I cannot control what IP address is the start point under "Public Proxied Subnet/Nat Routed" There is no way for me to edit the address there and the address displayed is not in the range of my static IP's. Have you tried enabling the "Public Proxied Subnet/Nat Routed" feature and plugging in the subnet mask provided (255.255.255.248)? Based on your PPPoE login your ISP should then route the IPs they assigned to you. If you did try that, what addresses showed up in your address allocation list?
--
Assiduus usus uni rei deditus et ingenium et artem saepe vincit |
|
loudog1327
join:2009-11-06
Wheaton, IL | Well I have tried that but I do not get IP addresses that are part of my static block. |
|
muiredised
ESSE QUAM VIDERI
join:2007-06-11
Tacoma, WA
| said by loudog1327 :Well I have tried that but I do not get IP addresses that are part of my static block. One possible cause of that is a misconfiguration on the part of your ISP. When you enable the proxied subnet and put in the subnet mask your ISP gave you their router should forward public IPs to you based on what they assigned to your PPPoE login. If they have something misconfigured in your build they will have to correct it.
At one time, in Illinois (Ameritech region) you had to add the word "static" to your PPPoE login username. At that time it was something like whatever@static.sbcglobal.net, but a call to your ISP would definitively answer that question.
--
Assiduus usus uni rei deditus et ingenium et artem saepe vincit |
|
loudog1327
join:2009-11-06
Wheaton, IL
| Well after using the suggestions from the forum here on my ip scheme, I did have everything setup properly, I still had the issue and got in touch with ATT and the 2WIRE team at att, they also verified everything was set correctly and it was mentioned that others have had the same issue with the IP not being pingable, they sent a tech out whole swapped me for a netopia. |
|
muiredised
ESSE QUAM VIDERI
join:2007-06-11
Tacoma, WA
| said by loudog1327 :...they sent a tech out whole swapped me for a netopia. Heard more than a few similar stories. It is a shame that these 2wire mysteries tend to go unsolved.
--
Assiduus usus uni rei deditus et ingenium et artem saepe vincit |
|
qtfoo
join:2004-12-03
Gilbert, AZ
1 edit | Not a mystery at all. You hit the nail on the head in your last post. ATT only uses sticky static now for the most part, only legacy customers have the Wan/Lan, dhcp static, or basic static builds.
Since the OP is located in IL he needed to authentication @static. to pull his correct sticky-static gateway. Then he would enable public proxied subnet and enter subnet mask. At that point he could go to edit address allocation and under WAN IP Mapping he would have his block of 5 IP addresses(8 total including broadcast, net block, and gateway which may not appear)
Enabling public routed sub interface will only cause problems when dealing with sticky statics
My assumption is that the OP wasn't authenticating with the @static.
The first thing that should of been checked was to check to see if hes getting the correct static gateway(broadband link > internet address). |
|
