|
|
| Bitas2 2003-08-10, 3:11 pm |
| I have 2 w2k servers on LAN for training purposes. One is domain with 2 NIC. It's connected to LAN and internet. I had ICS and it's worked fine. I've decided to setup NAT. On domain I've installed NAT and in both connections moved to NAT on RRA, also marked public connection to translate tcp/udp headers. On second server also made NAT and moved connection. Everything works except that second server doesn't get ip address automaticly. If I'm setting it manually works ok, but automaticly no. Why server doesn't get ip address from dhcp server? It's installed on first server.
thanx for help | |
| nero64 2003-08-11, 9:18 am |
| MS TK pg 752
"Do not use NAT on a network with other windows 2000 server domain controllers, DNS servers, gateways, DHCP servers, or systems configured for static IP because of the possible conflict with other services."
I think this might relate to your case but what you have said i can't understand fully. If you have a NAT server shouldn't it be setup statically anyway. ie the connection to the LAN. | |
| Bitas2 2003-08-13, 5:55 am |
| The other server isn't DC, DNS or DHCP server. Also i have XP Pro on LAN and it doesn't obtain IP address automaticly from NAT. | |
| jocampo 2003-08-13, 8:36 am |
| quote:
Originally posted by Bitas2
The other server isn't DC, DNS or DHCP server. Also i have XP Pro on LAN and it doesn't obtain IP address automaticly from NAT.
Ok...let's see....
In NAT, client does not obtain IP automatically at least you setup NAT Server to do that: you must go to the ADDRESS ASSIGMENT TAB on NAT Server Properties, then, check the "automatically assign IP" box.
You also can setup a DHCP on your subnet instead using NAT as IP allocator and it is more useful.
It is important that your NAT client is in the same subnet that NAT Server or DHCP Server; this is important in order to get the IP address without problem. Also, for client to use NAT, DNS resolution must be well configured.
Check this link:
http://support.microsoft.com/defaul...kb;en-us;310357 | |
| Bitas2 2003-08-14, 3:42 pm |
| The problem was that address pool on dhcp server was too small (192.168.0.2-10) and server01 took them all. I've extended address pool (192.168.0.2-100) and lan works fine. But I don't get it. What for server needs 10 ip addresses? Also second server took 10. Only XP pro leased only 1 ip address.
Thanx in advance for explanation.
Bitas | |
| jeff_j_black 2003-08-14, 4:23 pm |
| You may have other RRAS ports that automatically take those addresses. You can reduce or eliminate unwanted RRAS ports and free up that block of addresses. | |
| jocampo 2003-08-14, 4:35 pm |
| quote:
Originally posted by Bitas2
The problem was that address pool on dhcp server was too small (192.168.0.2-10) and server01 took them all. I've extended address pool (192.168.0.2-100) and lan works fine. But I don't get it. What for server needs 10 ip addresses? Also second server took 10. Only XP pro leased only 1 ip address.
Thanx in advance for explanation.
Bitas
NAT gets 10 leases from DHCP for Nat clients, automatically. These leases are not bring back to DHCP Server; they remain on NAT 'till you put off it. There is one registry key thay you can modify in order to get more or less leases from the DHCP, but i do not remember where it is. | |
| Bitas2 2003-08-15, 5:13 am |
| Could you explain how exactly i can reduce or eliminate unwanted RRAS ports and free up that block of addresses?
Thanx | |
| Jonoplunk 2003-08-15, 12:49 pm |
| Open the RRAS Admin window, highlight Ports and right click the select Properties. You can then select a device and click Configure and untick the Remote Access Connection box.
Alternatively you could open your RRAS Servers Properties box and create a Static Address pool for the RAS server. You would need to pay attention to make sure they are on the correct subnet mask, and that they did not clash with your DHCP servers range. May be an idea to create Exclusions to prevent the DHCP from assigning duplicate addresses. |
|
|
|