Can Not Assign A Static IP

We just had a T-1 line installed with an Adtran 616 CSU/DSU, we are trying to
assign our Windows Server 2003 a static IP, and we are getting errors of
duplicate gateways. We are routing fromt he Adtran to a 3COM office connect
VPN Firewall (with a public static IP) to the server. If we use DHCP we can
get to the web fine, the moment I try to put a public IP on the server I get
errors and nobody can get to the web. The Adtran also has a public IP.
Before the T-1 we just used DHCP, and there were no issues. We need our
server to have a static IP for some applications that we run. Any help would
be greatly appreciated.

We really need more detail of how these devices are connected. If the
server is behind the firewall (ie on the LAN connected to the firewall's
"private" interface) you cannot give it a public IP. You would only be able
to connect to the firewall's public IP(s) from the Internet.

A simple diagram would help.

Scott L. wrote:
> We just had a T-1 line installed with an Adtran 616 CSU/DSU, we are
> trying to assign our Windows Server 2003 a static IP, and we are
> getting errors of duplicate gateways. We are routing fromt he Adtran
> to a 3COM office connect VPN Firewall (with a public static IP) to
> the server. If we use DHCP we can get to the web fine, the moment I
> try to put a public IP on the server I get errors and nobody can get
> to the web. The Adtran also has a public IP. Before the T-1 we just
> used DHCP, and there were no issues. We need our server to have a
> static IP for some applications that we run. Any help would be
> greatly appreciated.

Here may be a few steps to help you:
1) go to the DHCP's server configuration.
2) Find the IP Address Range it assigns clients
3) Make the static IP Address not in the range

This may help or not i had a problem with my server 2003 when I used a
static ip address for some of the applications i was using and i read about
it and assigned it a static ip address not in the ranged of the DHCP Server
an it work well.

"Bill Grant" <not.available@online> wrote in message
news:u4riwF$(E-Mail Removed)...
> We really need more detail of how these devices are connected. If the
> server is behind the firewall (ie on the LAN connected to the firewall's
> "private" interface) you cannot give it a public IP. You would only be
able
> to connect to the firewall's public IP(s) from the Internet.
>
> A simple diagram would help.
>
> Scott L. wrote:
> > We just had a T-1 line installed with an Adtran 616 CSU/DSU, we are
> > trying to assign our Windows Server 2003 a static IP, and we are
> > getting errors of duplicate gateways. We are routing fromt he Adtran
> > to a 3COM office connect VPN Firewall (with a public static IP) to
> > the server. If we use DHCP we can get to the web fine, the moment I
> > try to put a public IP on the server I get errors and nobody can get
> > to the web. The Adtran also has a public IP. Before the T-1 we just
> > used DHCP, and there were no issues. We need our server to have a
> > static IP for some applications that we run. Any help would be
> > greatly appreciated.
>
>