Computers cannot connect to domain

inode

i have one other workstation connected to windows server 2003 Small business. it connects without any problems. but when i try to connect any other computers it says the domain cannot be found. even when i use the same cat 5. both computers have the same version of windows pro sp2. anyone know any reason why these other workstations cannot connect?

Thomas_S_Hunterson

Is the correct domain name set in network settings?

inode

every setting in the network settings is the same as the workstation that can connect.

aFlabbyPanda

are you using the connect computer wizard or the manual way (computer properties) method of joining the network

majiktripp

I have found that when adding machines to domains sometimes you need to place .local at the end of the domain name,it seems to aid in the discovery of the domain server.Don't know why exactly but when using the Add to Domain wizard (as I recommend as allows you to add Administrator account on machine) type the domain name with .local on end(ie.work.local) and see if that works.

_CreeD_

Make sure the DNS entries match those of the working PC. Are you using DHCP, is the DNS record correct? If static do they have unique IP addresses (even if you do not connect both clients at the same time this would cause a problem with ARP, the only reason I'd see why this might even happen though is a test lab, you could run ARP-a * the clear the cache on the server each time you swap clients but really if this is the case just use 2 unique addresses).
If the DNS server is correct (your 2k3 server) on the problematic machine try pinging the servers IP, if that works ping it by name. If that works then DNS should be okay. If the latter doesn't work but your DNS settings are correct then run IPCONFIG /FLUSHDNS on the problem client.

inode

thanks for the help will try this tommorrow and post results

stevenmu

Check that the PCs which don't connect can ping the server and the one that does, also check that they can ping each other.

zod

your DNS server in tcp/ip should be the windows server

inode

ok im here now. all the dns settings are correct. i cannot ping any computer on the network. it is really strange. i am, connected through a switch. im totally confused as to why this isnt working

SouperComputer

inode wrote:

ok im here now. all the dns settings are correct. i cannot ping any computer on the network. it is really strange. i am, connected through a switch. im totally confused as to why this isnt working

Maybe clear the arp cache.

Also, could be a physical problem, dodgy NIC, cable or port on switch. Switch out the NIC (or add one if onboard) and take it from there.

inode

i first thought it was the NIC but then i tried my laptop(which previously worked) and had no success. tried the same cat5 as the workstation that did work and had no success. also did a flush. i know the NIC work as broadband is connected through the swirch and all the computers are working with that...

The_Goose

Maynbe stupid but its hardly the firewall on the machine?

aFlabbyPanda

what switch and NIC's is it? try setting the link speed of the NIC to match the swtich (usually either 100 full or half)

_CreeD_

The firewall would have to be majorly buggered to be that restrictive though you're right it is worth checking. If it's working on your Broadband connection it sounds a lot like it's on the wrong subnet. I know you've answered a lot of this in bits and drabs but it would really help if you could condense your setup information.

You have broadband, is it via a router connected to the clients via a switch? If so are the clients getting their IP settings from it or is your SBS Server a DHCP server (Run IPCONFIG /ALL on the clients and see if the IPs of the DHCP servers are the same). If they are BOTH giving IPs you have a problem, you only need one on your subnet. The way it should ideally be setup is your Router is not the DHCP server (using the SBS server gives you more control and better use of the advanced service advertisements). In the DHCP properties make the router's IP your default gateway, make your SBS server (presuming it's your DNS source) the primary DNS but use your ISP's DNS server as your secondary (unless you've done a lot of work on your own DNS server to get it to forward requests to the internet etc.).

ScumLord

Are you using a seperate user account for the new pc or the same one? does the 2nd computer have a computer account?

Sounds like the IP settings on the PC, manually set this up to a working IP on the server I always found that if you let it do it automatically it never worked. It's been ages since I went near server though once I got everything working I just left it to it's own accord and preaty much forgot everything to do with it.

SouperComputer

is this an existing setup that has gone wallop, a new machine being added to an existing setup or is it a complete new domain?

inode

tried everything. decided then to format server and start from scratch. worked a treat. everthing is up and running now :-) thanks for all the help