Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 778
  • Last Modified:

Netvanta 3200 is preventing clients on remote network from updating from my new DHCP server

I've disabled my old DHCP server and setup a new one.  All my clients on my local network are now requesting leases from my new server no problem.  However  I have a T1 from here to my house with a Netvanta 3200 on each side connecting the two networks (same subnet and everythign).  I didn't configure these at all and I know very little about them but I have a feeling they are causing the problem with the clients on my remote network from updating DHCP.  

When I try a IPCONFIG /RENEW command on a client on the remote network I get the error An error occurred while renewing interface Local Area Connection : unable to contact your DHCP server. Request has timed out.
When I do IPCONFIG /ALL it still shows my old DHCP server.  These are the only clients that do so.

These netvantas are not DHCP servers, all they really do is pass traffic between the networks.  I have about 4 days left on the DHCP leases for these clients before they quit working unless I can figure out why the Netvantas are allegedly blocking the DHCP update.

Here is the config for the HOST netvanta (one on my host network):
!
!
hostname "localNetVanta"
enable password *********
!
ip subnet-zero
ip classless
ip domain-name "domain.local"
ip name-server 192.168.200.6 
no ip routing
!
event-history on
no logging forwarding
no logging email
logging email priority-level info
!
username "atadmin" password "*********"
username "admin" password "**********"
!
banner motd #
                 ****** Important ******

Enable and Telnet passwords are configured to "password".
Please change them immediately.

The ethernet 0/1 interface is enabled with an address of 10.10.10.1
Telnet access is also enabled.



#
!
ip policy-timeout tcp telnet 0
!
!
!
!
!
!
!
!
!
!
interface eth 0/1
  description localNetVanta
  bridge-group 1
  ip address  192.168.200.28  255.255.255.0 
  no ip route-cache
  no shutdown
!
!
!
interface t1 1/1
  description localNetVanta
  clock source internal
  tdm-group 1 timeslots 1-24 speed 64
  no shutdown
!
interface ppp 1
  bridge-group 1
  ip address  192.168.200.28  255.255.255.0 
  no ip route-cache
  mtu 1520
  no shutdown
  cross-connect 1 t1 1/1 1 ppp 1
!
!
!
!
!
no ip tftp server
ip http server
ip http secure-server
no ip snmp agent
no ip ftp agent
!
!
!
bridge 1 protocol ieee
!
!
!
!
!
!
line con 0
  no login
!
line telnet 0 4
  login
  password **********
!
end

Open in new window


Here is my config for the remote netvanta on the remote network:
!
!
hostname "remoteNetvanta"
enable password ********
!
ip subnet-zero
ip classless
ip domain-name "domain.local"
ip name-server 192.168.200.6 
no ip routing
!
event-history on
no logging forwarding
no logging email
logging email priority-level info
!
username "atadmin" password "********"
username "admin" password "********"
!
banner motd #
                 ****** Important ******

Enable and Telnet passwords are configured to "password".
Please change them immediately.

The ethernet 0/1 interface is enabled with an address of 10.10.10.1
Telnet access is also enabled.



#
!
ip policy-timeout tcp telnet 14400
!
!
!
!
!
!
!
!
!
!
interface eth 0/1
  description remoteNetvanta
  bridge-group 1
  ip address  192.168.200.29  255.255.255.0 
  no ip route-cache
  no shutdown
!
!
!
interface t1 1/1
  clock source internal
  tdm-group 1 timeslots 1-24 speed 64
  no shutdown
!
interface ppp 1
  bridge-group 1
  ip address  192.168.200.29  255.255.255.0 
  no ip route-cache
  mtu 1520
  no shutdown
  cross-connect 1 t1 1/1 1 ppp 1
!
!
!
!
!
no ip tftp server
ip http server
ip http secure-server
no ip snmp agent
no ip ftp agent
!
!
!
bridge 1 protocol ieee
!
!
!
!
!
!
line con 0
  login
!
line telnet 0 4
  login
  password **********
!
end

Open in new window


Anyone see whats going on?  Again these netvantas only provide a connection.  No DHCP is done by them, it should be handled by my physical DHCP server
0
DrPcKen
Asked:
DrPcKen
  • 8
  • 5
1 Solution
 
Jan SpringerCommented:
Does the new machine have the same IP as the old machine?  Have you cleared the arp cache?  Do you have "ip helper" configured?  Have you updated that address?
0
 
DrPcKenAuthor Commented:
New dhcp is a different address.

No I have not cleared arp cache (is that in my firewall?).  I'm not sure about "ip helper" either.  I'll try and find out.
0
 
Jan SpringerCommented:
"ip helper" relays udp packets to the server specified.
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
DrPcKenAuthor Commented:
Where would I configure this?  On DHCP server? DNS?
0
 
Jan SpringerCommented:
On the netvanta -- to tell the netvanta where to forward udp packets for dhcp relaying.
0
 
DrPcKenAuthor Commented:
Ok thanks! I'm looking for a command reference now for ip helper.  Would I need to do this on both netvantas?
0
 
DrPcKenAuthor Commented:
Also, which interface on which netvanta should i put the ip helper on? eth0? t1 1 or ppp 1?

Thank you!!
0
 
Jan SpringerCommented:
I would for consistency.
0
 
DrPcKenAuthor Commented:
which interface would the ip helper comand go on? I have  eth0, t1-1 and ppp-1?
0
 
Jan SpringerCommented:
You put it on the interface to which the packets first arrive.  (eth0)
0
 
DrPcKenAuthor Commented:
got it. Thank you! Trying now
0
 
DrPcKenAuthor Commented:
Thank you!
0
 
DrPcKenAuthor Commented:
That did it perfectly! Thank you for your help!
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 8
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now