• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 198
  • Last Modified:

network browsing

I will try to discribe this as best as I can.  I have a win2k server running and 2 clients currently on the network.  I have a hub with all computers connected to it and an uplink running into a router.  
until the money comes available to build a second box, I I have a domain set up and I am wanting to run all services on the one server system.
I am wanting to run  DHCP, WINS, DNS, FTP, and Exchange.  This is going to be a nightmare to accomplish if it is possible to run all these services on the same box.
 
Exchange is working fine and so it seems DHCP and FTP.  
The DHCP server is giving out IP leases fine to the client systems(this also includes the wins and DNS server information).  The weird this is that the clients can not ping or tracert back to the server even after they are assigned ip addresses from the server.  Basiclly they get the IP from the server and then they are dead in the water.  
I have a DHCP pool of 192.168.1.100-150 (available if needed later on) with 192.168.1.115-192.168.1.125 as the reservation. The server's ip address is 192.168.1.115.
So right now it does not look like DNS is working or working properly and that WINS is doing nothing for me.  
I have also been dealing with functionality recently that at times a netbios ping of any client or the server from any seat will generate a reply from the routers or my ISP assinged ip.  This seems to happen whenever I try to add an external DNS server setting to the computers.
Can someone please help me in determining what could be causing the clients to get IPs from the DHCP server and then not be able to browse the network or what setting need to be adjusted for this enviroment to work properly?

If you need any more information please let me know and I will provide aditional information
Jon
0
Jondexter
Asked:
Jondexter
  • 5
  • 3
  • 3
  • +2
1 Solution
 
frankaCommented:
can you give an ipconfig -all of the server and the clients?

can't you ping an IP or a DNS name?
what happens with nslookup?
0
 
HousenetCommented:
-You have to authorize the Dhcp server for the LAN..
-Have all the client stations use the 2000 servers INside IP for dns resolution.
-On the DNS server , delete the root zone ...looks like a(.)... & specify your ISP's (or router's IP if thats whats typically done) dns server IP's in the forwarders tab (dns server properties)..
-You should use dhcp options.. 003 (inside IP of server), 006(inside IP of server),015(2000 LAN Domain name),44(inside IP of server) & 46 (0x8)...
0
 
JondexterAuthor Commented:
franka
I can ping by IP not by DNS name
all clients right now only have the internal DNS server assigned to them
Housenet I will try your options tonight when I am infront of the server.  will let you know of status as soon as I try it
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

 
HousenetCommented:
"all clients right now only have the internal DNS server assigned to them" Make sure this applies to the server as well.... ISP or Nat-box-router's IP should only be listed in the forwarders tab in DNS server properties..
0
 
JondexterAuthor Commented:
franka
I can ping by IP not by DNS name
all clients right now only have the internal DNS server assigned to them
Housenet I will try your options tonight when I am infront of the server.  will let you know of status as soon as I try it
0
 
JondexterAuthor Commented:
the server only has the ip address of 192.168.1.115.  So do the clients.  
0
 
HousenetCommented:
-Did you remove the root zone ?
0
 
JondexterAuthor Commented:
NSLOOKUP also does not receive any reply.
the root zone had been removed and I also went through all the DHCP settings listed above but there has still not been any change in the client server relationship.
0
 
frankaCommented:
you can be quite sure that the problem is on your DNS server not with the communication between client and server.

Check Netdiag.exe (/fix). You must
install Support Tools from the Windows 2000 Server CD-ROM to run Netdiag.exe.

BTW: it is a very common problem having trouble with DNS. So check also the various helps at ms:

http://support.microsoft.com/support/kb/articles/Q260/3/71.ASP
http://support.microsoft.com/support/kb/articles/Q298/4/48.ASP
0
 
frankaCommented:
in most cases it is the best way to delete you current zone and make a new one with the wizard.
Make sure that the DCs can re-register their SRV records.
0
 
JondexterAuthor Commented:
None of the above items where able to resolve the issue I had.  I eventually had to format and reinstall server on the system.  After doing a good back up before hand.  Afer installing Server and exchange and getting the services back up and running (DHCP,DNS,WINS), everything is working like a charm.  There was definatly something else going on there.  Don't sure what it was, but it is taken care of now.
0
 
cempashaCommented:
Jondexter,
No comment has been added lately (642 days), so it's time to clean up this TA.
I will leave a recommendation in the Cleanup topic area for this question:

RECOMMENDATION: PAQ/Refund

Please leave any comments here within 7 days.

PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!

Thanks,

cempasha
EE Cleanup Volunteer
---------------------
If you feel that your question was not properly addressed, or that none of the comments received were appropriate answers, please post a request in Community support (with a link to this page) to refund your points. http://www.experts-exchange.com/Community_Support/
0
 
moduloCommented:
Finalized as proposed

modulo

Community Support Moderator
Experts Exchange
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 5
  • 3
  • 3
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now