XP & 2000 users that use static ip's in one office & dhcp in another office
We have clients that have laptops with a static IP in one office & use dhcp in the main office. These are some bat files that can be used to switch from static to dhcp & back so they can log on to either part of the domain with as little inconvenience as possible. All the client has to do is double click the appropriate .bat file for thier location. These have saved me a lot of time changing configs when the clients are in the main office.
The dhcp bat is:
netsh interface ip set address "Local Area Connection" dhcp
The Static bat is:
netsh interface ip set address "Local Area Connection" static 127.0.0.1 255.xxx.xxx.xxx 127.xxx.xxx.xxx 1
The first series of numbers is the IP, the second series is the Subnet Mask, the third series is the Gateway, & the last number is the multiplier
And of course you create these in notepad & save as dhcp.bat & static.bat.
or you can name them by location Topeka.bat & Lawrence.bat
There is also a .bat to check the config after you run one of the batch files which is:
Netsh interface ip show config
pause
Also see ...
Internet Connection Sharing
H3To enable Internet Connection Sharing on a network connection follow these steps./H3PBR br /First, span style="font weight: bold"Open Network Connections. /span br / br /Click the dial up, local area network, PPPoE, or VPN connection you want to share, and then, under Network Tas
H3To enable Internet Connection Sharing on a network connection follow these steps./H3PBR br /First, span style="font weight: bold"Open Network Connections. /span br / br /Click the dial up, local area network, PPPoE, or VPN connection you want to share, and then, under Network Tas
NT/2000/XP: Display or view the Windows routing table
H3During troubleshooting and system configuration, it is sometimes helpful to get a look at a host's routing table. This recipe describes viewing the routing table from the command prompt in Windows./H3PFrom a command prompt, type the following command to view the complete routing table: br
H3During troubleshooting and system configuration, it is sometimes helpful to get a look at a host's routing table. This recipe describes viewing the routing table from the command prompt in Windows./H3PFrom a command prompt, type the following command to view the complete routing table: br
NT/2000/XP: Add a temporary route to the Windows routing table
H3A route describes the gateway IP address and network interface to use when sending packets to a network. The routing table on a host holds a list of destination networks and the routes to those networks. This recipe describes adding entries to this routing table that will not persist following
H3A route describes the gateway IP address and network interface to use when sending packets to a network. The routing table on a host holds a list of destination networks and the routes to those networks. This recipe describes adding entries to this routing table that will not persist following
Home Network Troubleshooting Tips
H3This is another of my ongoing recipes. This recipe contains useful ingredients and methods to troubleshoot network problems. We all have them. : )/H3Pspan style="font weight: bold"Wireless Networks/span br / br /I run a 802.11G wifi at home and know the pains at times of using wire
H3This is another of my ongoing recipes. This recipe contains useful ingredients and methods to troubleshoot network problems. We all have them. : )/H3Pspan style="font weight: bold"Wireless Networks/span br / br /I run a 802.11G wifi at home and know the pains at times of using wire
How to Install the Netbeui Protocol on a Windows XP
H3This article describes how to install the NetBEUI protocol on a Windows XP based computer. This may be useful because the NetBEUI protocol is not included in the list of installable protocols in Windows XP even though the files that are needed to install the protocol are included with the instal
H3This article describes how to install the NetBEUI protocol on a Windows XP based computer. This may be useful because the NetBEUI protocol is not included in the list of installable protocols in Windows XP even though the files that are needed to install the protocol are included with the instal