<div>
If yopu are part of a Windows Domain....<br />
A policy in AD could block that out for a computer.<br />
<br />
Log on &nbsp;to the computer and open a cmd window<br />
Do a gpresult<br />
<br />
compare it to a gpresult on anther computer in the domain, see if there are differences.<br />
If there are, is the computer in the same OU as the other, what policies are and are not being applied etc...
</div>


If yopu are part of a Windows Domain....
A policy in AD could block that out for a computer.

Log on  to the computer and open a cmd window
Do a gpresult

compare it to a gpresult on anther computer in the domain, see if there are differences.
If there are, is the computer in the same OU as the other, what policies are and are not being applied etc...

<div>
I would maybe reinstall the drivers, or try the Roll Back Driver option in Device Manager &gt;&nbsp;Network Adapters &gt;&nbsp;right-click on Adapter Name &gt;&nbsp;Properties &gt;&nbsp;Driver TAB.<br />
<br />
Might even want to just try updating the drivers for your particular adapter.<br />
<br />
Rob
</div>


I would maybe reinstall the drivers, or try the Roll Back Driver option in Device Manager > Network Adapters > right-click on Adapter Name > Properties > Driver TAB.

Might even want to just try updating the drivers for your particular adapter.

Rob

<div>
<div class="content wysiwyg-content">
Hi All,<br />
<br />
We had a recent hang on a windows server 2003 SP 2 system. We had to power cycle the box and when it rebooted we discovered that it no longer had it's network configuration.<br />
<br />
If you got to set the TCP/IP properties it refuses to accept any thing but dhcp which won't work in our situation.<br />
<br />
My background is unix/linux so forgive me if I'm not calling something by its correct name.<br />
<br />
Has anyone seen this or better yet have a solution for it?<br />
<br />
Thanks,<br />
<br />
Mike
</div>
</div>


Hi All,

We had a recent hang on a windows server 2003 SP 2 system. We had to power cycle the box and when it rebooted we discovered that it no longer had it's network configuration.

If you got to set the TCP/IP properties it refuses to accept any thing but dhcp which won't work in our situation.

My background is unix/linux so forgive me if I'm not calling something by its correct name.

Has anyone seen this or better yet have a solution for it?

Thanks,

Mike

Network control panel no longer allows manual setting of TCP/IP Properties

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.

Microsoft Legacy OS

Networking software modules are interfaced with a framework implemented on the machine's operating system that implements the networking functionality of the operating system. The best known frameworks are the TCP/IP model and the OSI model. Systems typically do not use a single protocol to handle a transmission. Instead they use a set of cooperating protocols, sometimes called a protocol family or protocol suite.[9] Some of the best known protocol suites include: IPX/SPX, X.25, AX.25, AppleTalk and TCP/IP. Other protocols indirectly related to networking include the hypertext transfer protocol (HTTP) and its related technologies, Dynamic Host Configuration Protocol (DHCP), Domain Name Server (DNS) and other Internet protocols.

Networking Protocols

System Utilities are a type of system software used to support the computer infrastructure, distinguishing it from application software which is aimed at directly performing tasks that benefit ordinary users. Commonly used utilities include password managers, disk managers, system monitors, data synchronization tools, security and antivirus software and editors.