Win2k3 Group policy

  • Thread starter Thread starter Marc Reynolds [MSFT]
  • Start date Start date
M

Marc Reynolds [MSFT]

Group policy doesn't have anything to do with this problem. Is the hub
plugged into a cable modem or dsl modem? Is the modem also assigning DHCP
addresses? What are some examples of the IP addresses the clients are
receiving?

--

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.
 
marcello said:
The Hub is connected to the cable modem,

I do not think (am not sure) the Modem [Motorola SB5100] is assigning IP
addresses. Nonethless, the Ip addresses from the clients are 24.0.xxx.xxx,
which is different from the ip address of the server (67.xxx.xxx.xxx). These
two have different gateways also.
Click to expand...

Thats a cable modem and does not put out dhcp scopes.

Disconnect cable to modem and assert that clients then receive your dhcp
scope lease addresses accross hub. Specify the local DNS server's ip_address
in dhcp lease options. Clients should not use an ISP's DNS server to resolve
addresses. The local DNS server needs to have its root zone deleted and
forwarders configured.
How can I ensure that the clients obtain the IP addresses that I specify?
Click to expand...

By installing a firewall or filtering pakets in the case somebody is running
a DHCP server outside the cable modem.
Another thing I tried -- using the group policy -- is using logon scripts to
map a network drive from the client, somehow it never gets executed.

If I double click on the vbs file, am able to map the network drive.
Click to expand...

Is this a domain or workgroup? Did you create users on the server/domain?
 
I agree. You need to separate your private network from the Internet. All
the chattering that domain members and servers do amongst each other is not
something you want routed over the Internet (and it won't work anyway.)

Plus you probably have wide open file/print shares.

Easiest solution is to go buy yourself a standard cable/dsl router (which
has a built in switch) and throw the hub out. If you really want to, you
can uplink the hub to the switch and use it if you need more ports to plug
machines into.


--
Colin Nash
Microsoft MVP
Windows Printing/Imaging/Hardware



SaltPeter said:
marcello said:
The Hub is connected to the cable modem,

I do not think (am not sure) the Modem [Motorola SB5100] is assigning IP
addresses. Nonethless, the Ip addresses from the clients are 24.0.xxx.xxx,
which is different from the ip address of the server (67.xxx.xxx.xxx). These
two have different gateways also.
Click to expand...

Thats a cable modem and does not put out dhcp scopes.

Disconnect cable to modem and assert that clients then receive your dhcp
scope lease addresses accross hub. Specify the local DNS server's ip_address
in dhcp lease options. Clients should not use an ISP's DNS server to resolve
addresses. The local DNS server needs to have its root zone deleted and
forwarders configured.
How can I ensure that the clients obtain the IP addresses that I
Click to expand...
specify?

By installing a firewall or filtering pakets in the case somebody is running
a DHCP server outside the cable modem.
Another thing I tried -- using the group policy -- is using logon
Click to expand...
scripts
to
map a network drive from the client, somehow it never gets executed.

If I double click on the vbs file, am able to map the network drive.
Click to expand...

Is this a domain or workgroup? Did you create users on the server/domain?
marcello
Click to expand...
Click to expand...
 
I have installed win2k3 enterprise server, it is connected to a HUB like all
the clients.

The HUB is connected to a modem.

The Win2k3 server is also the DHCP server, however the clients are obtaining
their own IP addresses that are not in the specified scope.

any hints.

Marcello
 
The Hub is connected to the cable modem,

I do not think (am not sure) the Modem [Motorola SB5100] is assigning IP
addresses. Nonethless, the Ip addresses from the clients are 24.0.xxx.xxx,
which is different from the ip address of the server (67.xxx.xxx.xxx). These
two have different gateways also.

How can I ensure that the clients obtain the IP addresses that I specify?

Another thing I tried -- using the group policy -- is using logon scripts to
map a network drive from the client, somehow it never gets executed.

If I double click on the vbs file, am able to map the network drive.

marcello
 
Back
Top