Help! Lost in the forrest ? or NAT issue?

[Guest]

Group,

I have a small network (about 10 Clients) that I'm trying to get a net
connection to.
I setup a server w/ Win2k3 and standard 192.168.x.x IPs and DHCP the
clients. I belive I got the DNS and DHCP working because clients are getting
they're IPs from the scope. I did setup DNS in AD and setup the domain
"xyz.loc" for the clients. For the net connection I set up a Cisco router to
NAT out the local IPs. Unfortunately I'm at basic levels in Cisco's IOS.
Under some configs I do get Global outside IPs for the clilents however the
client still can't get Net. I was woundering if there is something in AD that
needs to be done or that I'm missing. We were given a few static IPs from our
ISP (Verizion) and on a DSL line.

I was curoius if any one out there has a similar situation: Win2K3, local
DHCP, DNS on AD to Static IP DSL line w/ NAT to Net... With so many
acronyms no wounder I'm confused..

Any ideas or suggestions would be greately appreciated. I just want to get a
minimum config working so I have something to default to as I fine tune it.

I can say that I have a whole new respect for MSCE's and CCIE's

 

[Doug Sherman [MVP]]

The two most likely issues are:

1. Routing: The clients must be configured with the internal IP of the
Cisco router as their default gateway. You can pump this out with DHCP -
scope option #003. If your clients cannot ping an Internet IP - eg.
4.2.2.1, you have a routing issue.

2. DNS: In an Active Directory domain, both the DC and all clients must
point to the DC's IP address for Primary DNS. Again you can pump this out
with DHCP scope options - #006. However, in order to resolve Internet
names, you must enable Forwarders on the DC/DNS server. Open the DNS
console, right click on the Forwarders tab, check the box to enable
forwarders and add the IP address of your ISP's DNS server. If the
Forwarders tab is greyed out, delete the "." zone. If you can ping 4.2.2.1,
but you cannot ping google.com, you have a DNS issue.

Doug Sherman
MCSE, MCSA, MCP+I, MVP

 

[Doug Sherman [MVP]]

Sorry: "Open the DNS console, right click on the Forwarders tab" Should
be: Open the DNS console, right click on the server, select Properties,
click on the Forwarders tab.............

Doug Sherman
MCSE, MCSA, MCP+I, MVP

 

[Guest]

Thanks Doug,

The cause was that simple default gateway setting on the
clients.. All works on those now..

I do have one Win 2000 Pro as client that for some reason
doesn't work.. The win XP's do. All are set to DHCP and
with that default gateway.. Any ideas there?

I just initially looked at it.. Haven't really got in to it yet.

 

[Doug Sherman [MVP]]

For a fair test, run ipconfig /release on the Win2k machine and reboot it.

Doug Sherman
MCSE, MCSA, MCP+I, MVP