UREGENT - Domain Unavailable Somthimes. 1

[SteveAudus]

Dear All please help,

Can you explain this.

Using new 48 laptops that have a wired and wireless connections,the Wireless connection has a static IP address, and finds the domain ok, but the wired connection picks up it's IP from DHCP on the server, but when asked to connect to the server it can't logon to it,
and it can not ping the server... how & why!!!!!

We have been asked to log all machines using wired connection to pull now a policy setting that does not seem to pulled down when using wireless connection... is this b*****ks or what!!!!

Please help this is driving us nuts?

http://www.chaucer.sheffield.sch.uk

 

[abrannon]

Can you give more detail on the problem?

What error message do you get when trying to connect to the domain through the Wire?

 

[SteveAudus]

I can't quote the excate error.
But it's the one where the domain is unavaiable.
and wired you can not ping the server.

Thanks for your help

http://www.chaucer.sheffield.sch.uk

 

[AustinPowers]

Hola,

I'd look into the Subnet Mask settings...

Hope this helps!

AP

 

[gazzanewpy]

Are you sure DHCP is working correctly? Have you tried a workstation to check the cabling?

If you cannot ping then the issue is often cabling or the network card since this implies a hardware fault. HAve you checked the device manager to ensure your ethernet card is set correctly?

First, set a static address on the wired port to one within the same range as the server itself. Then restart (XP shouldn't need this but best to be safe than sorry) and try to ping the server. If nothing, recheck the IP and subnet mask of both the server being pinged and the workstation itself. If both of these are correct and still nothing, have your cabling checked out. Also, disable or remove your wireless card whilst doing all this to ensure that the system is not getting confused!

Policies do not seem to be carried over wireless - I am still trying to find a solution to this one myself. Best we have found is to reduce your reliance on policies for all laptop users (especially since the policies that do follow across can cause issues when using the laptops away from the network). Try forcing them through the command prompt using GPUPDATE /FORCE - this might help (we have had limited success with this over wireless).

Hope this helps.

 

[GlenJohnson]

I like to start with the basics. First, check your cabling as mentioned earlier. Second, on a wired machine that can't ping, do ipconfig and see if the ip address is 169.254.x.x, which would mean dhcp probably isn't working. (I'd normally suggest pinging local host, but since it's more than one machine, chances are it's not the nics.) Third, try a fixed ip as was suggested earlier. I'd also take a machine that is wired, install a wireless nic and see what happens. Good luck. You may want to try a few tricks like pathping and see where you lose your connections.

Glen A. Johnson
"To fear the worst oft cures the worse."
William Shakespeare (1564-1616); English dramatist, poet.

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884

 

[SteveAudus]

Thank you for all your suggestions, I will try them.

gazzanewpy thanks for the GPUPDATE tip, never heard of that.
Cheers

Steve

http://www.chaucer.sheffield.sch.uk