General discussion

Locked

clients not connecting to the server

By ashirumusediq ·
some clients not connecting to my server within the intranet give error " no domain server found etc".the server can be browse to see the clients but cannot connect to the client gives" network path not found".few that can connect to the server are very slow and hang when copy/open any share file on the server. ihave re and check the tcp/ip config,cabling,new hub and nic, reinstalled the os with sp6 for third time now.
can it be the software or what.
pls help my job is on the line.

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

clients not connecting to the server

by McKayTech In reply to clients not connecting to ...

On our network, we have seen similar problems where the underlying cause was either a WINS configuration issue or a matter of having to remove the workstations from the domain and add them back in. For example, you can see this if the WINS client on your WINS server does not point to itself for both primary and secondary addresses and you end up with split registrations (in a multi-server environment, particularly).

If you can share a little more about the network (single server?, PDC?, WINS, DHCP, what protocols?) and the workstations (Win98?, WinNT, W2K?), I'm sure you'll get some good ideas of things to check.

paul

Collapse -

clients not connecting to the server

by ashirumusediq In reply to clients not connecting to ...

The question was auto-closed by TechRepublic

Collapse -

clients not connecting to the server

by Magetower In reply to clients not connecting to ...

Here are a few things to check (not knowing your setup... :) )

1. Since you are running TCP/IP you should be using WINS. If you are running DHCP then make sure the WINS server addresses are included in the DHCP settings (global or scope specific depending on your setup). Also make sure your PDC/BDC, WINS, DHCP servers are using static or reserved addresses. Make sure the WINS server is pointing to itself in its TCP/IP settings.

2. Once the WINS is straightened out you are still having problems with some of the workstations (NT I presume) open the Server Manager on the PDC and attempt to access the workstations from there. If you get errors then the workstation's trust with the domain has been lost and you will have to remove and re-add the workstation to the domain.

3. If your BDCs are on different subnets from the PDC make sure they can 'see' each other (even if this requires using the LMHOSTS file) as this can cause account replication errors.

hope this helps...

Collapse -

clients not connecting to the server

by ashirumusediq In reply to clients not connecting to ...

The question was auto-closed by TechRepublic

Collapse -

clients not connecting to the server

by soliboy In reply to clients not connecting to ...

I agree with the two boys above. Either a WINS issue or: The RPC binding order in the registry(of the clients) may also be set wrong, ie. TCP/IP is down the list compared to any other installed protocols, so the clients may be timing out resolving names. See MS technet for changing the RPC binding order. I can't remember properly off the top of my head. PS: check out that there is no device eg. webramp/router or whatever on the network that is running DHCP (you'd never know).

Collapse -

clients not connecting to the server

by ashirumusediq In reply to clients not connecting to ...

The question was auto-closed by TechRepublic

Collapse -

clients not connecting to the server

by ashirumusediq In reply to clients not connecting to ...

This question was auto closed due to inactivity

Back to Windows Forum
7 total posts (Page 1 of 1)  

Related Discussions

Related Forums