Sunday, December 14, 2008
Thursday, December 4, 2008
Wednesday, December 3, 2008
Tuesday, December 2, 2008
Monday, November 24, 2008
Thursday, November 20, 2008
Thursday, November 13, 2008
Thursday, November 6, 2008
Wednesday, November 5, 2008
Friday, October 31, 2008
Wednesday, October 15, 2008
Tuesday, October 7, 2008
MACBA de nit
DHCP server database migration
Steps to migrate a DHCP server database migration from a Windows 2003 Server to Windows 2003 Server.
In the source server, log in as local or domain administrator account.
1.- click Start -> Run
2.- type "cmd" and then press Enter
3.- type the next line:
netsh dhcp server export C:\dhcpdatabase.txt all
4.- stop DHCP server service
Now, log in as local or domain administrator in the new dhcp server.
1.- copy dhcpdatabase.txt from remote system to local filesystem in C:\dchpdatabase.txt.
2.- be sure you have dhcp server service running. (If you don't have it then you need to install it.)
3.- click Start -> Run
4.- type "cmd" and then press Enter
5.- type the next line:
netsh dhcp server import C:\dhcpdatabase.txt all
Finally you only have to authorize the dhcp server.
For detailed info you can visit the reference.
References:
http://support.microsoft.com/kb/325473/
In the source server, log in as local or domain administrator account.
1.- click Start -> Run
2.- type "cmd" and then press Enter
3.- type the next line:
netsh dhcp server export C:\dhcpdatabase.txt all
4.- stop DHCP server service
Now, log in as local or domain administrator in the new dhcp server.
1.- copy dhcpdatabase.txt from remote system to local filesystem in C:\dchpdatabase.txt.
2.- be sure you have dhcp server service running. (If you don't have it then you need to install it.)
3.- click Start -> Run
4.- type "cmd" and then press Enter
5.- type the next line:
netsh dhcp server import C:\dhcpdatabase.txt all
Finally you only have to authorize the dhcp server.
For detailed info you can visit the reference.
References:
http://support.microsoft.com/kb/325473/
Tuesday, September 30, 2008
route - show / manipulate the IP routing table
Actually I'm using a Debian Lenny with kernel $(uname -r) 2.6.22-3-686.
Sometimes I'm surfing the web through my job's wired connection and I get an error like "Page not found etc. blah blah blah". Why? The answer is my routing table changes automatically when a non-protected wireless connection is found. I don't need wireless connection when I'm working... let's take a look to my corrupted routing table:
berlin:/home/parra# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 eth1
192.168.0.0 * 255.255.255.0 U 0 0 0 wlan0
link-local * 255.255.0.0 U 1000 0 0 eth1
default 192.168.0.1 0.0.0.0 UG 0 0 0 wlan0
default 192.168.0.254 0.0.0.0 UG 0 0 0 eth1
First of all I need to shut down the wireless interface:
berlin:/home/parra# ifdown wlan0
After this I need to remove the lines with wlan0 interface in the table, the command is (2 times because I have 2 interfaces):
berlin:/home/parra# route del default
berlin:/home/parra# route del default
Now I have this routing table:
berlin:/home/parra# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 eth1
link-local * 255.255.0.0 U 0 0 0 wlan0
link-local * 255.255.0.0 U 1000 0 0 eth1
I need to remove the second line cause it's using wlan0 interface:
berlin:/home/parra# route del -net 192.168.0.0 netmask 255.255.255.0 dev wlan0
After all this boring stuff... I need to restore the default gateway for my wired connection:
berlin:/home/parra# route add default gw 192.168.0.254
berlin:/home/parra# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 eth1
link-local * 255.255.0.0 U 1000 0 0 eth1
default 192.168.0.254 0.0.0.0 UG 0 0 0 eth1
It's done. Parra.
Sometimes I'm surfing the web through my job's wired connection and I get an error like "Page not found etc. blah blah blah". Why? The answer is my routing table changes automatically when a non-protected wireless connection is found. I don't need wireless connection when I'm working... let's take a look to my corrupted routing table:
berlin:/home/parra# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 eth1
192.168.0.0 * 255.255.255.0 U 0 0 0 wlan0
link-local * 255.255.0.0 U 1000 0 0 eth1
default 192.168.0.1 0.0.0.0 UG 0 0 0 wlan0
default 192.168.0.254 0.0.0.0 UG 0 0 0 eth1
First of all I need to shut down the wireless interface:
berlin:/home/parra# ifdown wlan0
After this I need to remove the lines with wlan0 interface in the table, the command is (2 times because I have 2 interfaces):
berlin:/home/parra# route del default
berlin:/home/parra# route del default
Now I have this routing table:
berlin:/home/parra# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 eth1
link-local * 255.255.0.0 U 0 0 0 wlan0
link-local * 255.255.0.0 U 1000 0 0 eth1
I need to remove the second line cause it's using wlan0 interface:
berlin:/home/parra# route del -net 192.168.0.0 netmask 255.255.255.0 dev wlan0
After all this boring stuff... I need to restore the default gateway for my wired connection:
berlin:/home/parra# route add default gw 192.168.0.254
berlin:/home/parra# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 eth1
link-local * 255.255.0.0 U 1000 0 0 eth1
default 192.168.0.254 0.0.0.0 UG 0 0 0 eth1
It's done. Parra.
Tuesday, September 16, 2008
Pizza Pepe!
Friday, September 5, 2008
Mont-Ral, Tarragona
Subscribe to:
Posts (Atom)