DNS DHCP RAS

  • Thread starter Thread starter Georgios N. Manolopoulos
  • Start date Start date
G

Georgios N. Manolopoulos

POSTED ALSO IN WIN2000.NETWORKING

Network structure info:
I have a small office network with the following configuration
-2 DC (W2k AdvSe SP4)
1. Acting as DNS, DHCP, RRAS and Gateway (ISA incl) to the
internet (via permanent DSL connection/static IP)
2. Acting as Exchange, Web and File Server (is also Firewall client,
Exchange, Web, FTP etc works fine)
Both GC (probably dont need this for my conf)
Acive Directory seems to work ok (synchronisation etc)
-6 internal client PCs all WXP SP1a (all DHCP enabled)
-1 Network plotter
-2 remote laptop users with WinXP SP1a connecting via VPN (DHCP enabled)
DCs have static IP addresses (private range)
Network plotter and clients use DHCP (ipconfig list correct DNS, Server IP
settings)
I use VPN for remote users to connect to my resources.

This is the scenario:
In the office one laptop user (winXP) connects to the domain.
His machine is full member of the directory, gets its address from DHCP
(reserved IP for that machine) and registers to the DNS. (I am not using
WINS) Everything is ok...
User leaves office (switches off his machine), connects later remotely via
VPN. User can browse only via \\othermachinenames.
Remotely connected machine is only viewable in the Netwrok Neigbourhood at
the RAS, DC, other clients in the office can not browse the remote machine
via \\remotemachinename BUT through \\remotemachineIPaddress .Ipconfig on
the remote machine gives correct dns server results etc.Remote machine can
browse the network through \\othermachinenames but sees only its name under
network neigbourhood.
The IP that the remote machine gets from DHCP when connected remotely is NOT
the one reserved for that machine in the DHCP configuration.
I am a newbie...but this beginns to annoy me...(i am doing something wrong
probably...)
Is there a way to configure the DHCP to give specific addresses to remote
clients?
Can I force DHCP to give to the remote machine the same IP as it is reserved
for that machine when connected locally, meaning that IP of that machine is
the same whether connected remotely or locally?

Thank you all for your time...
 
Hello Georgios,

I believe the problem you are running is due to the fact that your DC is
multi-homed.

Please take a look at this article for help on how to get around the
problems
with name resolution on a multi-homed DC.

http://support.microsoft.com/default.aspx?scid=kb;en-us;292822&Product=win2000

Also it is not a good idea to have your DC running on an ISA Server
especially
since you have another DC.

Finally, regarding configuring DHCP to give addresses to remote VPN clients
is a simple configuration within the RRAS configuration to obtain addresses
from the DHCP
Server.

Hope that helps.

--
Thanks,
Mohanchand Koduri [MSFT]

When replying, please post to GROUP so that everyone can benefit from the
knowledge.

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm


--------------------
 
Thank you for the help
Regards
GNM


Mohanchand Koduri said:
Hello Georgios,

I believe the problem you are running is due to the fact that your DC is
multi-homed.

Please take a look at this article for help on how to get around the
problems
with name resolution on a multi-homed DC.

http://support.microsoft.com/default.aspx?scid=kb;en-us;292822&Product=win20
00

Also it is not a good idea to have your DC running on an ISA Server
especially
since you have another DC.

Finally, regarding configuring DHCP to give addresses to remote VPN clients
is a simple configuration within the RRAS configuration to obtain addresses
from the DHCP
Server.

Hope that helps.

--
Thanks,
Mohanchand Koduri [MSFT]

When replying, please post to GROUP so that everyone can benefit from the
knowledge.

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm


--------------------

Georgios N. Manolopoulos said:
POSTED ALSO IN WIN2000.NETWORKING

Network structure info:
I have a small office network with the following configuration
-2 DC (W2k AdvSe SP4)
1. Acting as DNS, DHCP, RRAS and Gateway (ISA incl) to the
internet (via permanent DSL connection/static IP)
2. Acting as Exchange, Web and File Server (is also Firewall client,
Exchange, Web, FTP etc works fine)
Both GC (probably dont need this for my conf)
Acive Directory seems to work ok (synchronisation etc)
-6 internal client PCs all WXP SP1a (all DHCP enabled)
-1 Network plotter
-2 remote laptop users with WinXP SP1a connecting via VPN (DHCP enabled)
DCs have static IP addresses (private range)
Network plotter and clients use DHCP (ipconfig list correct DNS, Server IP
settings)
I use VPN for remote users to connect to my resources.

This is the scenario:
In the office one laptop user (winXP) connects to the domain.
His machine is full member of the directory, gets its address from DHCP
(reserved IP for that machine) and registers to the DNS. (I am not using
WINS) Everything is ok...
User leaves office (switches off his machine), connects later remotely via
VPN. User can browse only via \\othermachinenames.
Remotely connected machine is only viewable in the Netwrok Neigbourhood at
the RAS, DC, other clients in the office can not browse the remote machine
via \\remotemachinename BUT through \\remotemachineIPaddress .Ipconfig on
the remote machine gives correct dns server results etc.Remote machine can
browse the network through \\othermachinenames but sees only its name under
network neigbourhood.
The IP that the remote machine gets from DHCP when connected remotely is NOT
the one reserved for that machine in the DHCP configuration.
I am a newbie...but this beginns to annoy me...(i am doing something wrong
probably...)
Is there a way to configure the DHCP to give specific addresses to remote
clients?
Can I force DHCP to give to the remote machine the same IP as it is reserved
for that machine when connected locally, meaning that IP of that machine is
the same whether connected remotely or locally?

Thank you all for your time...
Click to expand...
Click to expand...
 
Back
Top