W2K Server & Linksys issues

[Enkrypted]

I have a small network consisting of a W2K Advanced Server and 4 Windows XP Workstations. The way it is currently setup is:

1. Cat5 cable going from DSL modem to WAN port on Linksys BEFSR41 router
2. W2K server and 2 workstations plugged into router
3. Cat5 cable going from uplink port on router to port on Linksys 5 port 10/100 switch
4. Other 2 workstations plugged into switch.

I currently have the DHCP client scope on the W2K server disabled and the DHCP function enabled on the router (had problems with it the other way). I changed the router IP address to 192.168.0.2. On the DHCP setup page within the router configuration I have my server's IP address listed in the first DNS box. I also have the starting address to be xxx.xxx.xxx.100.

When I go into computer management on the W2K server, under Services & Applications, the first listing is for DHCP. It has a white circle with a green dot inside of it. If I extend the tree beneath it, it shows the folder for the DHCP scope with a white circle with a red dot inside of it. Below that if I go to the DNS option and select the forward lookup zone for the server's domain name, I see 4 computer descriptions in the screen to the right. However it shows the listing for computers as:

User A : xxx.xxx.xxx.12
Server : xxx.xxx.xxx.101
User C (old name) : xxx.xxx.xxx.13
User C (new name) : xxx.xxx.xxx.13

All computers can ping the router at 192.168.0.2, and all computers can be seen in the contents of Entire Network and recieve internet access. However the only systems that can be accessed from each other are:

Server
User A
User B (not listed under DNS forward lookup zone)

When trying to access Users C & D, I recieve a message saying: \\(computername) is not accessible. The network path was not found. This just started happening today as yesterday everything was working fine.

I was wondering if you experts out there can help me figure out what I am doing wrong or suggest a better setup for the network, I would very much appreciate it. I know that this is probably not the best way to setup a network, but more of a temporary solution until I can get better equipment/setup. I was thinking about purchasing a D-Link switch (DSS-24+ model) and throwing another network card into the server and running through ISA 2000. Any suggetions are appreciated.

I have posted this thread in several different forums, hopefully I can get some insight on this. Thanks.

Also...sorry if this doubleposts...

Enkrypted
A+

 

[bcastner]

If it was working and then stopped working, it suggests a hardware problem, not the need to change your software configuration.

 

[mattjurado]

Also, because you have such a small size network, I wouldn't bother with DHCP. Just give each client a static IP, gateway, and DNS entry that points to the 2k server. Make sure that your ISPs DNS servers are entered in the properties of your server in the DNS tool.

Matt J.

Please always take the time to backup any and all data before performing any actions suggested for ANY problem, regardless of how minor a change it might seem. Also test the backup to make sure it is intact.

 

[bierhunter]

Since all machines can ping the router, your DHCP assignments are working (at least for the address and gateway).

If you enter "ipconfig /all" on the problem machines, are they getting all of the correct addresses for DNS, etc?

Also, pinging by \\<name> is using netbios name resolution instead of regular DNS. Try pinging just by the IP address itself from the other machines. The problem here may just be Windows related. If you can ping by IP address but not by computer name, then your problem sounds like a netbios name resolution problem.

Since your DHCP isn't from the server, it's not integrating the IP assignments into Active Directory; and since the DNS server looks confused, that could be your connectivity problem when pinging by name. It sounds like the clients aren't registering themselves properly in the Active Directory DNS.

There are a lot of possibilities depending upon how your Win2k network is setup.

Using Active Directory, you normally don't need WINS, since DNS handles that in AD; but this may be helpful to troubleshoot. Bring up WINS service on the server and add that to your DHCP settings. Release and renew the clients and see if they can start to see each other by name.

 

[Enkrypted]

***UPDATE***

I was able to correct the problem. I had to remove each computer from the domain and delete the computer entry under AD. After deleting the computers, I rejoined each computer to the domain again and now they can all browse the network properly.

Enkrypted
A+

 

[YokyDoky]

I have a very similar setup at home - W2K Server, several workstations. I used the server as the router once upon a time, with RASPPPoE which is infinitely better than that Enternet PPPoE provided by the telco. (This assumes you use DSL.) I'm on my second Linksys router now, the first one had the Net2Phone feature set and lasted about 2 years. ISA is a major resource hog so unless your server has at least a half-gig of RAM and doesn't do much else I'd stick with your current setup. Of course, ISA is much more configurable and powerful than the Linksys box, but you pay for it.

Y. Doky - &quot;Manager&quot; of Systems

&quot;A .22 caliber intellect in a .357 Magnum world.&quot;