Static IP and DHCP 1

[persim]

Im servicing a small network with a server nt4.0 and several workstations. Because of some app. we need static ip adressing. All workstations are connected trough a switch.

The company got access to wireless lan. This "box" on the wall is giving out ip adresses to be able to connect to the
internett. How do I solve this problem? Keeping static IP adresses and for the workstations to be able to "see" the ISP's wireless lan?

Best regards Per

 

[Jixer]

If you only need to access the app with static IP through the LAN the easiest way would be to get a Linksys Cable/DSL router.

Connect the Linksys router to the box on the wall that is providing the static IP and set the local IP of the Linksys to one on your network. Configure your DHCP server to use the IP of the Linksys as the gateway.

 

[SF18C]

Also look into DHCP reservations...the only PC/Server that NEEDS a static is the DHCP server!!! Everything else can be DHCP. Reserves are set by the MAC address and are always given the same IP.

SF18C
CCNA, MCSE, A+, N+ & HPCC

"Tis better to die on your feet than live on your knees!"

 

[justcurious]

If your workstations are configured with static addresses, they will never ask the "box" on the wall for an IP address so there should be no problem here.

Just make sure your Static IP settings match the network settings in the "box"s DHCP scope. For example, make sure they are all using the same network number, subnet mask, gateway and DNS server addresses that the box is trying to hand out. As long as they are on the same subnet, they will be able to see the box and use it as a gateway.

If it's really bothering you to have the box acting as a DHCP server, talk to a technical rep at the ISP and find out how to disable the DHCP service on their equipment. But, as I said, this should'nt be causing a problem with your current configuration.