New Network - non networked notebooks etc can't get access to it?

[speckytecky]

Recently we set up a new network. Move from Windows 2K server to 2003 Server didn't go as planned! Now trying to resolve a problem of teachers non networked notebooks and standalone PCs being able to see the new network and access resourse files printers etc. Any advice please?

[Bezwick]

Gonna need a lot more information to help you mate. Are you using DHCP? Are the clinets getting VALID IP addresses. If so can you ping anything on the network, if so what?
Can you lookup the dns servers? Are you using active directory?

[speckytecky]

Gonna need a lot more information to help you mate. Are you using DHCP? Are the clinets getting VALID IP addresses. If so can you ping anything on the network, if so what?
Can you lookup the dns servers? Are you using active directory?

Thanks for the speedy reply Bezwick.

Yes it is DHCP.

It's not a client problem as such but the notebooks that connect as standalones through the network so they are not in Active Directory.

From the notebooks I can ping the network OK, clean fast ping no problems there.

From printers and faxes I can't access the new network.

From run / my network/ Entire Network / MS Windows Networkn I can access the new network?

From

[PeterH]

If you're relying on network browsing to locate resources on your domain, you're likely to have problems. Try changing the workgroup name on your standalone laptops to match the NETBIOS name of your domain

Personally, I wouldn't depend on browsing the network to location resources. It's far easier to just type in UNC paths or create shortcuts. If your laptops aren't domain members, then you're also going to have issues with autnetication. You'll need to ensure that you have domain accounts with usernames and passwords that exactly match the local accounts on your latpops. Far better to make them domain members.

Peter

[plexer]

You mean that non domain member machines can't access things and not non-networked as a non-networked machine ain't even plugged in to the network?

Ben

[Gibbo]

It's not something silly like Windows Firewall is it?

[Michael]

The one thing comes to mind is security. Server 2003's default security is a lot more secure (by default) than Server 2000 security.

Your best bet would be to add these machines to the domain, but logon locally to the machines. You should then be able to authenticate against shares and printers using scripts or whichever method you use.

It doesn't sound like a DHCP problem as speckytecky can ping the DC.

[krisd32]

If theyr're not joined to the domain they won't show up in AD.
if there is any machines that are not on the network i do exactly as peterH has described with adding them to a workgroup of the same name as your domain and setting user account and passwords exactly the same as on your domain to sort out the authentication. and you should be working at that.

[pagelad]

When trying to use the resources you might have to physically type the names in,

Try using the FQN of the devices on the network,

So instead of "\\server1\printer"

you would use

"\\server1.<domain name>\printer"

Another neat trick is if you dont want to add the machine to the domain if you add the username \ password from the local machine to AD it with authenticate using that

[mpe]

If you're relying on network browsing to locate resources on your domain, you're likely to have problems. Try changing the workgroup name on your standalone laptops to match the NETBIOS name of your domain

It's also likely to help matters if your workstations have WINS and DNS configured to look at the server.