Windows 2000 network problem

I'm completely stumped! I am running a network of 10 computers. The server is running Windows 2000 Server, 8 client computers are running Windows 2000 Pro and 2 client computers are running Windows XP. The problem that I'm running into is that I can't get the XP computers to recognize the server to get access to network folders and printers, etc. The other 8 clients running 2000 Pro work just fine without any problems.

Does anybody know what my problem is???

 

Is this a Domain?
Or, a Workgroup?

 

I have to ask, XP Pro, right?

Domain, hopefully not for 10 clients?

You mean it won't browse or don't see them at all?

What happens if you search for computers?

You are sure the User and passwords and permissions are correct? Workgroup correct?

If so install NETBEUI on the XP's. It is not an uption untill you add it manually from the XP CD see:

http://support.microsoft.com/defaul...port/kb/articles/q301/0/41.asp&NoWebContent=1

Add also to 2K if not already there.

If the above don't do it then:

run

ipconfig /all >ipconfig.out

for each and post back in a message.

Mike

 

Clarify my last post!

Not all workstations

ipconfig of server, both XP's and 1 working 2k pro.

Mike

 

I wonder if this could be a master brousing issue?

 

none of those suggestions worked for me. The server is setup up as a domain and I double checked to make sure that the usernames, passwords and permissions are correct and they were. After that I installed netbeui and every computer in the network and I still have the same problem. all computers running windows 2000 work fine and the 2 running XP pro do nothing. When using the computers running windows XP, I tried doing a search for other computers on the network along with trying to search for the server. I came up with nothing at all. I even went through all of the component services on the server such as the computer browsing and everything that needs to be on is already running. Anyone else have any ideas?

Jesse

 

BTW can the 2k's server and pro see the XP's? Who can see who?

Humor me

Create a new user on one of the XP computers.

Make it exactly the same as the one used to log on to the server usename and password. EAXCTLY!

Log off this XP log back on as this user.

Try now!

Mike

 

I figured I had nothing to lose so I gave that a try. The username for the server was "jesrober" so I created a new user on the xp machine by the name of "jesrober ". The password on both of them was exactly the same and both computers were on the same workgroup "jobsearch ".

None of this helped, just the same old problem. The server won't recognize the machine running XP Pro and the XP Pro machine won't recognize the server. I'm probably starting to become a pain in the butt by now.


Jesse

 

OK!

No pain!

You do have link lights on the NIC and switch ports, right?

Do the XP's see each other?

When you said they were properly connected I may have assumed to much.

Get the LAN ip of one of the XP machines (like say 192.168.1.10)

Get the LAN ip of the server!

Now on server

ping 192.168.1.10 (whatever the reaal ip is)

then on XP

ping (servers IP)

what?

Now is the time to do the ipconfig /all

do it this way

command prmt

on server
ipconfig /all >server.txt

on one of the 2kPro
ipconfig /all >2kpro.txt

on one for one of the xp's
ipconfig /all >xp.txt

load each in of the files in wordpad etc and paste back in a message.

Mike

 

Check to see if the XP fire wall is turned on. It will drive you batty if it is.

 

XP workstations are much more DNS reliant than even 2K

Have you defined theIP address of the server as the DNS for the clients ? (You do of course have DNS as its a domain....)

 

Good point Andy,
Who ever is handling DHCP needs to be told to direct the clients to the server first for DNS and ISP DNS second.

 

All I want is some ping and ipconfig results!!!!

Then we will know about the DHCP and DNS!!!!!!!

mike

 

well I guess I'm still stumped. Here is my ipconfig information for a few of the machines on the network

Windows 2000 server machine

Windows 2000 Pro client machine

Windows XP Pro client machine

I hope this helps...


Jesse

 

sorry I gave the wrong links, I guess thats what happens when you get frustrated

Windows 2000 Server machine

Windows 2000 Pro machine

Windows XP Pro machine


Jesse

 

No wonder!

Are you doing something special with the XP's?

If not go to network properties tcp/ip and apply a specific IP in the same subnet. (in other words don't use DHCP on the 2 XP's)

Not sure how you have DHCP setup? Coming from router or a computer set as DHCP server. But this will bypass that!

So do this, find an open ip in the 198.xxx.xxx range and use it.

example
ip 198.xxx.xxx.xxx (find a free ip)
default gateway 198.110.201.3
DHCP none of course since you are had coding the ip
dns 198.110.192.40 and 198.110.193.10
wins none

If you missed this then I don't have confidence the rest is correct, but let us hope!

Do this on one XP, reboot and if everything else is correct you will connect!

If this corrects as it should then......

After this do the other IP with the same settings but with a different ip.

Mike

 

Dump NetBeui and replace it with TCP/IP.
Hope that helps.

 

Can't replace TCP/IP in XP because it can't be uninstalled in first place.

But he could get rid of NETBEUI if he knew how to set up the network.

But it won't hurt anything!


Mike

 

You guys are gods!! I finally figured out what my problem was.

I ended up getting rid of netbeui and changing all of the ip addresses on the xp machines and it worked great afterwords.

The ip address for this network was 198.110.201.xxx so I just changed the xp machines to have ip addresses within 198.110.201.xxx and that worked wonders. I did find out that to make the network drives I had to use the ip address instead of the server name.

for example instead of using \\jobsear3\database
I used \\198.110.201.190\database
and yes there are passwords on it so the security problems are not there

Thanks a lot guys, you are the greatest


Jesse

 

Hmmm

You figured it out, huh?

Looks like that was exactly what I told you to do!

I guess I just thought I figured it out!

The netbeui could have been left and would have allowed browsing by computer names. But by ip is slightly faster.

Glad it is fixed.

Good luck!

mike