📎 AI Summary:
The main issue discussed in this thread is that the user’s private server becomes inaccessible after restarting their Windows 7 computer due to IP configuration problems, specifically related to incorrect gateway settings. One contributor explains that the default gateway address appears outside the correct subnet range, and turning off an older server causes delays in network recognition, leading to connectivity issues. Solutions suggested include using host entries, broader subnet ranges, or DNS entries to improve stability during server restarts.
A

Ali Mohd

New Member
Member details
Joined
Mar 19, 2016
Messages
1
Thread Author #1
Hello!

i am using windows 7 with two different networks (.100.xxx - private server running windows server 2003) & (.1.xxx - Internet ). My IP settings are listed as follows:

-----------------------IP SETTINGS----------------------------

DHCP ENABLED : NO
IPv4 ADDRESS : 192.168.1.XXX (internet)
IPv4 SUBNET : 255.255.255.0
IPv4 ADDRESS : 192.168.100.XXX (private serve)
SUBNET : 255.255.255.0
IPv4 DEFAULT GATEWAY : 192.168.1.XXX
IPv4 DNS : 192.168.1.XXX (SAME AS GATEWAY)

----------------------IP SETTING-------------------------------

So when ever i restart my computer private server becomes inaccessible. i have remove the internet ip address to access my server then return back after. Please look towards my problem and help me to solve it.

Regards

Mohammed Ali
 

Solution
ussnorway
this is because the default gateway address is outside the subnets 254 ip range and turning off a older server like 03 means you must wait for all the rolls to reset before you can get an ip responce i.e, the server doesn't know it has an .100.X address yet... a host entry or wider subnet range would both solve it if speed is the key issue or a dns entry may be fine as a stop_gap until the server fully wakes.
Sort by date Sort by votes
ussnorway

ussnorway

Windows Forum Team
Staff member
Member details
Joined
May 22, 2012
Messages
4,599
#2
this is because the default gateway address is outside the subnets 254 ip range and turning off a older server like 03 means you must wait for all the rolls to reset before you can get an ip responce i.e, the server doesn't know it has an .100.X address yet... a host entry or wider subnet range would both solve it if speed is the key issue or a dns entry may be fine as a stop_gap until the server fully wakes.
 

Upvote 1 Downvote
Solution
You must log in or register to reply here.