playing with windows 7 I maanaged to get the following done.
Run windows update
Apply various GP's
Install software (from the network)
However, now i have semi-no access to the network at all.
When I log the machine on with a test user it complains that It cant find my redirected desktop and doesnt map any drives. I cant access the internet or manually map any drives at all. The machine was getting an address from DHCP
So, I remove the machine from the domain and attempt to re-join. It wont let me. Says that an AD controller cant be contacted.
I can ping the IP of both of my DC's fine. I can NSLOOKUP the IP's and it brings back the FQDN for both DC's fine...
Whats going on?
Windows firewall is turned off, all the features in homework group thingy are set to allow..
I just dont get why this machine suddenly wont see the network when everything is pingable...
Last edited by jamin100; 22nd May 2012 at 12:07 PM.
Yup, both on the servers and on the W7 machine
Machine is still picking up the same IP4 from DHCP too.
Last edited by jamin100; 22nd May 2012 at 12:11 PM.
then rationally the GP or software is interfering.
Try moving it a different ou?
if the problem is still present
Try resinatlling the above steps you have mentioned, without installing the software ?
between these steps did you reboot? could be a updated network driver being pulled from windows updates.Run windows update
We had a similar thing to this a few months ago.
The problem turned out to be a faulty piece of software which was being applied by Group Policy. The culprit software worked fine on WinXp, but had very strange problems on Win 7.
May be worth checking.
Can you remember what software it was for you on the off chance it may be the same here?
EDIT: Well just uninstalled that and restarted and it still doesnt work so its not that...
Really dont want to have to bin this installation and start from scratch but it looks like i may have too
Last edited by jamin100; 22nd May 2012 at 12:28 PM.
I would recommend disabling DHCP Server IPv6, as you're just going to use IPv4. I agree with others though that the DHCP client should be left alone so it can support IPv4 and IPv6.
I also agree with some network drivers from Windows Update being dodgy, although it was more of an issue on XP rather than 7. It's easy enough to roll back the driver if it has installed an updated version.
Reinstall the network driver maybe?
I had a pc which didnt like a dhcp address
Reinstalled Driver - Nothing
Reimaged = Nothing
Changed cables = nothing
Differnt Comp = Worked
New Motherboard from Dell = Nothing
Now im building it up running windows 7. And it all works...
A Common Fix for a lot of network issues that are a result of a software install is the following Command Line:
Commonly Antivirus software, such as sophos, avg etc interfere with the network cards and can cause semi-networked states, whereby you can see servers, but have weird issues such as being unable to join the domain, but it certainly hasn't been limited to just AV applications. I've seen network cards fail because of all sorts of applications.Code:netsh winsock reset
Go to your command prompt and type in the above command line and restart your computer. It's not always 100% but you might be surprised, can't tell you how many times this has sorted out weird network issues with clients.
Give it a try.
Note: This resets layer 3 protocols, giving your network card a nice refresh. Removing corrupt data (if any) potentially caused by hardware or software installations not officially compatible with your version of Windows O/S.
References: CCNA, Microsoft.com
Last edited by DEvans; 22nd May 2012 at 12:48 PM.
There are currently 1 users browsing this thread. (0 members and 1 guests)