Client machines unable to get Gateway address ? 1

[vrcatherine]

We have server (domain controller,DNS,DHCP,Proxy ..etc)
this will give away ip addresses to all the client
computers.
This is how its setup on server

Network card with public address

216.x.x.x.
255.x.x.x
216.x.x.1

DNS 172.x.x.x
172.x.x.x


Network card with internal(private IP address)

192.168.1.300
255.x.x.x
empty blank ( no gaetway)

DNS 192.168.1.300


Now everything is working clients gets the IP address
from the sever and they are able to logon to internet
without any problem.


Now only thing is

1) clients cannot ping to external IP address on the internet.( They cannot ping to any public ip address on
the internet).

When i check IP config on the client machines,it gives

192.168.1.303
255.x.x.x
empty blank( no gateway)


Does it has anything to do with my DNS settings on the
server ??


-- Cathy

 

[RobBoberts]

Yes, you have to have a gateway address in order to get to the internet.
No, getting an gateway address has nothing to do with DNS, however you will need to have DNS servers show up in ipconfig for it to work.
DHCP must not be vending the Gatway and DNS the workstations that can't get to the internet.

Televison will make radio obsolete.

 

[vrcatherine]

Ok, it has something to do with DHCP ??

Well clients are able to access internet , they
are able to browse web sites, emal ..etc

But when they say IPconfig they dont see the
gateway address .

 

[koquito]

somehow the are getting the gateway address, otherwise they wouldnt go to the internet.
Did you tried ipconfig /all ?
If you want to ensure they will receive it, then you have to configure the DCHP options to give out the address of the gateway.

A+, MCP, CCNA
marbinpr@hotmail.com

"I just know that I know nothing"
Socrates (469-399 B.C.E.)

 

[northerntech]

Koquito is right here when saying that the gateway address must received somehow. If not then the clients on your network are receiving their email just through the local intranet and what is looked at as browsing the internet is just information coming from the proxy server cache.

 

[justcurious]

Catherine, adding to what Koquito and northerntech have said, as odd as it may be, it sounds like your DHCP server is not configured with a gateway address.

Also, proxy servers, firewalls and routers can be configured to prevent ping packets from routing across networks. Your clients may have full Internet access while not being able to ping outside addresses.

 

[vrcatherine]

Thanks for the replies

I will check the DHCP and get back.

 

[vrcatherine]

I have a new problem now.

With client computers getting in to the domain.

We have got all new client computers and
they all are XP professional.

All these desktops get into Domain "ABC" without
any problem. Like i just go to My computer and
change the domain to "ABC" and it will immediately
ask me the Domain admin username/password and
once i give that, it will say "welcome to ABC domain"
and when i reboot the system works fine with the domain.

But the issue now is there are 3 systems which

2 Windows 2000 professional systems

1 windows 2000 server ( this is another system not my DC)


These systems when i try to join them on to the domain
it gives me the following error


"The following error occured attempting to join
the domain "abc".
The network path was not found.



Q) How can i resolve this ?

 

[ashpp]

Its a DNS problem.

Do a IPCONFIG on these stations, is DNS correctly showing the servers IP? Are they able to ping to the server by IP and name?

Also on the server you mention the IP address of its DNS server is
DNS 172.x.x.x
172.x.x.x

What kind of DNS server is this? Is it another Windows 2000 server?

 

[vrcatherine]

When i do a IPCONFIG on the client desktop(2000 professional)

it shows:

IP ADDRESS... 192.168.1.2
SUBNET MASK... 255.255.255.0
DEFAULT GATEWAY (empty --blank)


They are able to Ping to the server with
SERVER NAME & SERVER IP ADDRESS


The server has 2 NIC and external one has

EXTERNAL nic INFO:

STATIC IP ADDRESS

68.X.X.X
255.X.X.X
68.X.X.1

dns 151.x.x.x
dns2 151.x.x.x



INTERNAL NIC INFO:



192.168.1.300
255.X.X.X
empty

dns 192.168.1.100
dns2 151.x.x.x



This is a windows 2000 server where i have
configured the DOMAIN CONTROLLER,DNS,DHCP,, etc.

!!!

--Cathy

 

[RobBoberts]

Sounds like you are running a DNS server on 192.168.1.300, make sure 192.168.1.300 is listed as a DNS server on the win2k workstations you are trying to add to the domain. I would make it the primary DNS server. Better yet put it in DHCP so it is vended to your clients.

I assume 192.168.1.300 is not the real address because .300 would be an invalid number.

Televison will make radio obsolete.

 

[dholbrook]

The answer is in the IP address! If your system come up with 192.168.x.x, it means it is not able to obtain an address, and the system is automatically assigning itself an address in the 192.168 range. Started with WIn2000!

I would begin by checking your net card and net cable, and making sure it can even see the network. Then run ipconfig /release, followed with ipconfig /renew, to force the system to replace the 192 address with a real one. Check you network cables and the hub connection to make sure you have a good network connection (make sure the connection light is on on the hub/switch for that cable!). Step one, when it don't work, plug it in! Hate to say how many times the problem is just the cable is pulled loose in the connector, expecially when moving the systems around.

Also, when a system is the network gateway to the world, and has two NIC cards, (one to the WAN, one to the LAN) there should only be a gateway on the WAN card, otherwise the system will get confused when it tries to forward traffic. This Server's gateway needs to be on the card going out to the world (WAN), but the gateway address for all the other systems on the network (LAN) needs to be the address of the LAN card on the server providing the WAN access in order to pass the traffice in the correct direction.

HTH

David

 

[ashpp]

>The answer is in the IP address! If your system come up >with 192.168.x.x, it means it is not able to obtain an >address, and the system is automatically assigning itself >an address in the 192.168 range. Started with WIn2000!

No 192.168 is a standard private range which is very commonly used. Your thinking of 169.x.x.x which is automatically assigned by the machine if a DHCP server is unavailable.

 

[vrcatherine]

Hey Rob,

Bingo !!!!!!!!!!!!!!

It worked as what you had said.

I had added the 192.168.1.300 to the client computer's
DNS server setting and when i added the domain name
it went thru and joined me to the domain.

Now tell me one thing as you r saying:

>>I would make it the primary DNS server. Better yet put it >>>in DHCP so it is vended to your clients.


Can you guide me as how i can do this ?


--cathy

 

[RobBoberts]

Start:settings:control pannel:Administrative toolsHCP
Expand scope and highlight scope options, right click:configure options, scroll down to DNS servers, check the box and add the DNS server IP address. The workstation will not get the DNS server until they refresh there lease (probably take days) or you go around and release and renew the ip config on the workstations set up for DHCP. Maybe while you are at it you should add the gateway (it's listed as "router&quot.

Televison will make radio obsolete.

 

[RobBoberts]

Oh yea, don't forget to stop and start the DHCP service after you make the changes on the DHCP server.

Televison will make radio obsolete.

 

[ashpp]

Cathy,

I mean no disrespect but IP address ranges, and DHCP server options are elementary stuff for IT admin. You should really consider googling for the info, getting trained or reading a book.
It isn't fair to ask people questions that are fundanmental to your job without first doing some digging around yourself.
Anyhow, in the DHCP server, go the the Scope -> Scope Options -> and add the Option 006 DNS Servers with the IP address of your DNS server. (You can also do it in the Server Options this affects all scopes)

 

[vrcatherine]

Rob,

Hey it worked like magic.
I did the same thing and now
i can see the gateway (192.168.1.300)
in all the clients once they refresh the dhcp.

They are able to ping to outside address now


Great.
Thanks very much.

 

[vrcatherine]

Ashley,

Thanks for the advise.
I will start looking into the basics and
explore the stuff.

.--Thanks very much.

cathy

 

[ashpp]

No problem, I'm not trying to discourage you asking stuff - its just good to know the basics or you could get into deep trouble.

Still a little confused over the 192.168.1.300 address... are you positive the DNS server is configured to this? (It shouldn't be possible!)

Have a star Rob.