Windows 2000 DHCP

  • Thread starter Thread starter poolplayr
  • Start date Start date
P

poolplayr

Hi,

I am fairly new to a company and they have thier network set up like
this:

T1 -> static ip address on network card on server (dhcp disabled) a
second network card on the same server that is the lan side
(192.168.16.2) -> switch -> computers (users).

Therefore I have to assign new pcs an address because dhcp is off. When
it trys to come on and work it shuts its self off by saying in the
error log that another dhcp network has been detected at 10.*.*.* which
happens to becoming from the T1 box.

Today I tried putting in a router right after the T1 before the server
and statically entered the ISP information(tripled check that the info
was entered correctly). Then I turned dhcp off on the newly inserted
router and then turned DHCP on the windows 2000 server. Well the server
did dole out an ip address to the user computer of 192.168.16.30 so I
thought all might be well however I could not get the internet. On the
flashing computers (by clock) I was sending but not recieving.

There is a proxy, does that info need to go into the router
somewheres? It is a d-link 4 port router nothing fancy.

Or maybe there are some settings that have to be reset or adjusted on
the server now that it is acting as a dhcp server?

Help will be greatly appreciated.
 
Your DHCP scope options should include entries for your DNS server, router
(or proxy), WINS, etc.. Otherwise you'll have an IP address with no route to
anything else and/or no name resolution (outside of broadcast). To check you
settings:
ipconfig /all
Click to expand...

make sure you have the proper DNS/WINS/Gateway settings.

....kurt
 
poolplayr said:
Ok I will double check my scope settings. I have another question if I
may......

In this diagram (just like my setup is going to be)
http://www.smallbizserver.net/Network/TwoNicsastaticIPaddressISArouter/tabid/154/Default.aspx
is the routers DHCP disabled or should I keep it enabled?
Click to expand...

No, but it wouldn't matter anyway,...the "router" isn't going to even "see"
your network to begin with. Your network is hidden behind the SBS Server.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------
 
In that diagram, the server is a router/proxy something. The router is not
on your LAN, so DHCP won't work between the router and the workstations.

The usual small-network setup would be:

Router
|
Switch
| |
Server Workstations

Unless you need a cache/proxy/firewall box. If it's a Windows domain, DHCP
should be disabled on the router and enabled on the DC.

....kurt
 
Well thanks to you all I have gotten far. The network is now up and
running just like the diagram in the above link.

So boss man comes to me today and wants me to put a wireless router in
the network so he can use his laptop in the board room. So i got a 4
port wireless d-link router and hooked it up to my cat5 cable at my
desk. The routers default ip is 192.168.0.1. I know that I have to turn
the DHCP off on the wireless router cause its on my lan side but how to
make it work after doing that?

I thought it would be as easy as "pluging it in" and using it, however
this hasnt been the case i have been trying to get it to work for over
a 1/2 day. Can i have a wirless router on the lan side? If so how to
set it up right? My network addresses are the same as the diagram above.
 
Take the wireless router back to the store and exchange it for a Wireless
Access Point (WAP). You bought the wrong device for the job.

A WAP is just a wireless version of a Switch or Hub.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
 
Well i broke the VPN when I switched over to DHCP. I opened the PPTP
port on the router. Do I need to do anything else since DHCP is now
enabled and working?
 
poolplayr said:
Well i broke the VPN when I switched over to DHCP. I opened the PPTP
port on the router. Do I need to do anything else since DHCP is now
enabled and working?
Click to expand...

That doesn't have anything to do with DHCP.

Your design introduces a Back-to-Back DMZ between the Server and the NAT
Device which did not exist before. In the diagram at the link you first
gave the 192.168.1.x is the DMZ Segment which is "untrusted" and "external"
to the LAN. They can *not* directly communicate without using the NAT
functionality on the Server.

The NAT Device can no longer be the "VPN Server" because it is no longer "on
the LAN". You have to use VPN Passthrough on the NAT box and the Server now
must perform the job as a VPN Server.



--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------
 
Back
Top