NVG510 - How to configure Static IP for WAN and DHCP for LAN

[chrion777]

Can this be done? I see where you can make all of the LAN Public addresses, but how do we configure the router to have a static address and the LAN clients to have Private DHCP addresses. Our Company recently changed to AT&T and the tech did not configure it for Static IP. Our old public DNS entry is now pointing into the netherworld. I am trying to configure the router to use one of the 5 static addresses we have with some port forwarding for certain services exposed to one of our internal servers. I can see under Subnets & DHCP that you can expose a range to public addresses but this does not seem to accomplish what I am trying to do. This is the most confusing router I've ever seen. Please help!

[DonNewcomb]

I don't know if you can get a static IP. But you could sign up for a dynamic DNS service. ATT turned off the DDNS capability on my RG. I assume it's turned off on them all. What I did was to put the RG into router-behind-router mode and hook up my WRT54G2 which does support DDNS.

[chrion777]

I could use DDNS but would prefer not to. I want to use a static address and treat the gateway statically and I only need one public address. We don't need 7 IP's public. Just need our host name registered to one static address and everything else sitting on a private LAN. Port Fowarding to expose services we need accessible via internet.

[DonNewcomb]

ATT may offer that. I'm sure there'll be and additional charge. If not, let me know I'd like a static IP too. I think everyone who knows the difference would like one.  OBTW, There is a DHCP command that allows you to request a specific IP address. AFAIK it's not implemented in Windows. A buddy of mine told me that he used this on the Linux box he used as a firewall, gateway, server, etc. to keep the same IP address for years. No guarantee it will work but it's a thought.

[JefferMC ACE - Wizard]

---

DonNewcomb wrote:

ATT may offer that. I'm sure there'll be and additional charge (1). If not, let me know I'd like a static IP too. I think everyone who knows the difference would like one.  (2) OBTW, There is a DHCP command that allows you to request a specific IP address. AFAIK it's not implemented in Windows. A buddy of mine told me that he used this on the Linux box he used as a firewall, gateway, server, etc. to keep the same IP address for years. No guarantee it will work but it's a thought.

---

(1) Static IP blocks are available for an additional charge on most Uverse service plans.  Call and ask.  Some restrictions apply to the service.

(2) You would think so, but you would be wrong.  Some people who don't want to be trackable to a single fixed IP address like the anonymity of a dynamic IP address and have complained about how effictively-static most U-verse IP addresses are (i.e. while not guaranteed to do so, your external IP address will pretty much stay the same unless you replace the RG).

[chaakah]

This has to be the most Att-{Inappropriate content removed} router i have ever seen - who in the {Inappropriate content removed} wants to "dynamically" route ips?

The lack of 1 to 1 natting on this device is criminal.  They should just say we dont support multiple static public IP's

They need to issue a different modem - this is a joke.  The best part is once you open your internal IP's for "Dynamic public" ips - you then start getting IP conflicts internally

{Inappropriate content removed}

[TnIan]

I'm having the same problem as the original poster. With our previous DSL, we had a static IP that the modem automatically received every time it connected to the AT&T network. Everything behind the modem was assigned 192.168.1.x addresses from the modem's DHCP server. So we had a single public-facing IP, and we used port forwarding to get traffic where it needed to go on the LAN.

I'm having a frustrating time getting something similar set up on the NVG510. We have a block of 8 IPs that I set up in the "public subnet" section, and that's supposed to define the router's public address, but the broadband status page lists another public address, which confuses me. The instructions I got from AT&T tech support say I have to enable "public" as the DHCP range, but I don't want public IPs assigned to LAN nodes. There's an option to use the "private" DHCP range, but I don't know if that breaks anything.

And any which way, it Just Doesn't Work. I have port forwarding set up for 3389/TCP (Windows Remote Desktop Connection) and pointing towards a machine set up for remote access. I've tried both those public IPs in RDC, and it times out. This was working perfectly yesterday with our old DSL service & Netopia 3347 modem. I can RDC into that machine from the LAN, so I know the problem's not with the target PC. I just can't get it working through the NVG510.