G
Georgios N. Manolopoulos
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.
Q:
This applies to the remote clients via VPN.
Under network neigbourhood they can only see the computer name of the remote
client (the machine under consideration). They can connect via
\\othermachinename , exchange works fine, OWA is ok, intranet ok.
Why dont they get the complte list of copmuters in the domain under the
network neigbourhood?
It's more an issue of practicality rather than functionality, unless this
indicates a problem that I am not aware of.
TIA
-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.
Q:
This applies to the remote clients via VPN.
Under network neigbourhood they can only see the computer name of the remote
client (the machine under consideration). They can connect via
\\othermachinename , exchange works fine, OWA is ok, intranet ok.
Why dont they get the complte list of copmuters in the domain under the
network neigbourhood?
It's more an issue of practicality rather than functionality, unless this
indicates a problem that I am not aware of.
TIA