Select Page

How to fix Autoconfiguration IPv4 Address issue Windows Server 2012 r2

Today when i install Windows Server 2012 r2 OS in a new HPE Proliant DL 380 server, after the os installation i have added ip manually to the Ethernet interface, but i get a Limited Access error,so i double check the ip is correct or not, i was right ip is correct, so i disabled firewall ,then i checked by typing ipconfig in the command prompt and i get result as follows

 

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP Ethernet 1Gb 4-port 331T Adapter
Physical Address. . . . . . . . . : 3C-A8-2A-F3-CF-9C
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::f0e1:58c8:4e40:4513%12(Preferred)
IPv4 Address. . . . . . . . . . . : 10.60.148.43(Duplicate)
Subnet Mask . . . . . . . . . . . : 255.255.255.224
Autoconfiguration IPv4 Address. . : 169.254.69.19(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.60.148.33
DNS Servers . . . . . . . . . . . : 10.60.148.36
10.1.12.43
NetBIOS over Tcpip. . . . . . . . : Enabled

 

as you can see there is two ipv4 ip's , one is the ip which i given , second is APIPA range ip

 

to fix this please follow the steps

  1. Click on start and click on RUN (or simple press windowsKey+R ) type CMD
  2. type ipconfig

this is will give you following result

 

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP Ethernet 1Gb 4-port 331T Adapter
Physical Address. . . . . . . . . : 3C-A8-2A-F3-CF-9C
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::f0e1:58c8:4e40:4513%12(Preferred)
IPv4 Address. . . . . . . . . . . : 10.60.148.43(Duplicate)
Subnet Mask . . . . . . . . . . . : 255.255.255.224
Autoconfiguration IPv4 Address. . : 169.254.69.19(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.60.148.33
DNS Servers . . . . . . . . . . . : 10.60.148.36
10.1.12.43
NetBIOS over Tcpip. . . . . . . . : Enabled

now type below code in the command prompt

netsh interface ipv4 show inter

this will show you below resurlt

C:\\Users\\Administrator>netsh interface ipv4 show inter

 

Idx     Met         MTU          State                Name

---  ----------  ----------  ------------  ---------------------------

  1          50  4294967295  connected     Loopback Pseudo-Interface 1

 12          10        1500  connected     Ethernet

 13           5        1500  disconnected  Embedded LOM 1 Port 1

 14           5        1500  disconnected  Ethernet 2

 15           5        1500  disconnected  Embedded LOM 1 Port 2

 16           5        1500  disconnected  Ethernet 3

 17           5        1500  disconnected  Ethernet 4

 18           5        1500  disconnected  Embedded LOM 1 Port 3

 19           5        1500  disconnected  Embedded LOM 1 Port 4

 

 

 

check for the connected interface

from the above command result you can find the connected interface notedown its idx id which is 12 in my case but your id may vary , type following command with your idx id in the command prompt then press enter

netsh interface ipv4 set interface 12 dadtransmits=0 store=persistent

 

this will give you following result

C:\\Users\\Administrator>netsh interface ipv4 set interface 12 dadtransmits=0 store=persistent

Ok.

  1. Click on start and click on RUN (or simple press windowsKey+R ) type CMD and Type Services.msc a box will appear Search for DHCP client right click on it and Click on Properties click on Startup Type select Disable
  2. Now Click on Stop Button Below And click on Ok

* Note

  1. Unplug Your Lan Cable And Restart your System
  2. After Restart don't Plugin your Cable, Come again to Services.msc find DHCP client right click on it and Click on Properties click on Startup Type now select Automatic
  3. Click on Start button below and then Ok.
  4. Now Plugin your Lan Cable and Enjoy.

 

Network Bonding On Centos.

 

Network interface bonding is a Linux kernel feature which allows to aggregate multiple interfaces (eth0,eth1) into one virtual link such as bond0. Network card bonding is an effective way to increase the available bandwidth. If bonded the interfaces appears as same physical device and they have same MAC address. The other names for network interface bonding are port trunking, NIC teaming channel bonding and link aggregation. The main advantage of bonded network interface is to increase data throughput by load balancing and to provide redundancy by allowing fail over from one component device to another.

## How to create a network interface bond?

Create a file named ifcfg-bondN in the directory /etc/sysconfig/network-scripts, Here "N" is the number of interfaces. Then edit the contents of ifcfg-bondn and make it similar to the configuration settings for an Ethernet interface except  that DEVICE is set to bondn instead of ethn.

For example;

DEVICE="bond0"

IPADDR=192.168.1.121

NETMASK=255.255.255.248

NETWORK=192.168.1.0

BROADCAST=192.168.1.255

ONBOOT=yes

BOOTPROTO=none

USERCTL=no

TYPE=Ethernet

BONDING_OPTS="bonding parameters separated by spaces"

For each interface that you want to bond, edit its ifcfg-interface file so that it contains MASTER=bondN and SLAVE entries. An example is given below.

DEVICE="eth0"

NAME="System eth0"

IPADDR=192.168.1.101

NETMASK=255.255.255.0

BROADCAST=192.0.2.255

NM_CONTROLLED="yes"

ONBOOT=yes

USERCTL=no

TYPE=Ethernet

BOOTPROTO=none

DEFROUTE=yes

IPV4_FAILURE_FATAL=yes

IPV6INIT=no

PEERDNS=yes

PEERROUTES=yes

MASTER=bond0

SLAVE

Create the file bonding.conf in the directory/etc/modprobe.d/, so that it contain entry for each bonded interface, for example:

alias bond0 bonding

It ensures that the kernel loads the bonding module is loaded when bring up the bonded interface. All bonded interfaces require entry in this file.

# ip link set eth0 down >> bring interface down

# ip link set eth1 down >> bring interface down

# ip link set bond0 up >> bring interface up

HAPPY BONDING 🙂

How to remove WOUtempAdmin User Profile

I have got this error after updating system using WSUS Offline utility,after successful update system restarts And the login screen by default shows the username of WOUTempAdmin. Not a big deal as I can log in with my admin account. But still a pain.

to fix this issue you have to follow the steps:

Press "Windows Key" and "R"

type "regedit" press Ok

Run "regedit" this will open Registry Editor

Note* Be careful when editing the registry. Don’t go into the registry editor and delete anything or change a setting unless you know exactly what you’re doing. If you do know what you’re doing and are careful to modify only the correct values, you shouldn’t have any problems. However, if you start deleting folders (known as “registry keys”) or modifying other values, you could seriously damage your Windows installation. When using the registry editor, always bear this warning in mind.

Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon

 

Change DefaultUserName to your default user for eg: Administrator , i have used fragadmin0608 instead of Administrator this may vary

 

then within the registry you can find AutoAdminLogon

Press F3 and search for any entry containing "woutemplogin" and delete it as long as the searchphrase can't be found any more,then restart your system

After restart if you can see your login screen with your default username .then your issue is fixed

best of luck .

How to fix Unable to lock the administration directory (/var/lib/dpkg/) error in Linux

Some of you may experience this error in your life if you are using linux .it happens when previous installation fails , here is the screenshot which is happened in my Linux Distro

E: Could not get lock /var/lib/dpkg/lock – open (11: Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?

 its very easy to fix this error just type following commands in your terminal

sudo rm /var/lib/dpkg/lock  

this will delete the “lock” directory in /var/lib/dpkg/

after that you can install what ever you want

Enabling .Net Framework 3.5 in Windows Server 2012 using Command prompt

Enabling .Net Framework 3.5 in Windows Server 2012 using Command prompt 

You need

  1. Media of Windows Server 2012

insert your media in your dvd drive or mound it via iLo or pendrive

please not your drive letter which is assigned to that media

now open up your command prompt

press windows key and R key same time now run windows will appear  , now  type CMD  then press enter 

this will open your command prompt

now mound your drive letter

in this case my drive letter is  ”  D   “

so i need to type D: in the command prompt

now type following command

dism /online /enable-feature /featurename:NetFx3 /All /Source:d:/sources/sxs

Note*  in command line letter d may vary 



now wait for some time

done !

lets check on server manager

restart your server 

good luck 

Pin It on Pinterest