I would advice to set manual IP for all the pc's which are on lan.
Eg
Ip address: 192.168.1.1
Subnet : It will take by default
Default Gateway: 192.168.1.100
DNS: 192.168.1.100
Most of us highly recommend AGAINST using manual TCP configs; here's an example
of why:
Ip address: 192.168.1.1 This is a standardized address for a router not a workstation (the other one is at x.254)
Subnet : It will take by default ? Without DHCP, there is no default.
Default Gateway: 192.168.1.100 ouch! only one in 254 chances that this is correct and it's no known router's default address
DNS: 192.168.1.100may or may not work depending upon the vendor firmware forwarding DNS requests
DHCP is a one-time request at boot or first network access time, sets the tcp config and then
disappears entirely. Dynamic TCP is the most reliable means to get a vaild and stable network connection.
The SOLE exception is were you need one system to be at a known location for
others to access, ie: a server address. The right way to setup a lan with server(s) is:
- set manual addresses for the server at the high end of the range
- set the others to DHCP and limit the ip range to less than the lowest server address
If you have SRVR-A and SRV-B, the set A= 192.168.1.200 and B= 192.168.1.201.
Now in your router, restrict DHCP address range to 192.168.1.2 thru 192.168.1.199
Life will be good
If you want to ensure access by name, add these two lines to
\windows\system32\drivers\etc\host with notepad:
192.168.1.200 srvra
192.168.1.210 srvrb
save the file and then copy to all your systems. Life will even be better
prototype_nsx said:
ip add 192.168.1.1
subnet 255.255.255.0
dns 192.168.1.1
wins 192.168.1.1
default gateway 192.168.1.1
client pc:
ip add 192.168.1.2
subnet 255.255.255.0
dns 192.168.1.1
wins 192.168.1.1
default gateway 192.168.1.1
most of us have lan's with routers; eg
Code:
modem---router---systemA
+---systemB
and the above easily conflicts with the default router address of linksys routers. The above would work ONLY when the systems
are NOT attached to a router, but only each other using a cross-over cable; eg
keep your life simple: a router belongs at x.x.y.1 and systems at y.2 -> y.254
y.0 and y.255 are broadcast address so don't even thing of using these.
If you visit the Network forum, you will see that one of the first things recommended
for connection issues is to update the router firmware and the network adapter drivers. This frequently solves 80% of the issues.
GAMING places heavy stress on our routers and that is why there are some models specifically marketed as
gaming routers.