New
#31
Umm... is this solved?
zzz2496
Alternate IP Address causing Domain connections to drop
-
-
New #32
I don't think you can open the subnet any further. The mask is 255.255.255.0.
But ya, it looks solved for now as he's typing the IP address into the UNC to connect to the network resources.
-
New #33
You can open subnet anyway you want, surfasb...
Subnet mask works like this:
255.255.255.0 = 11111111.11111111.1111111.00000000 (24 ones, and 8 zeros, called 24 bit subnet).
I can have 11111111.11111111.11111110.00000000 (23 ones, and 9 zeros, called 23 bit subnet) as my subnet, the Decimal representation would be 255.255.254.0.
Or I can have an 8 bit subnet:
11111111.00000000.00000000.0000000 (8 ones, 24 zeros, 8 bit subnet), decimal representation will be 255.0.0.0.
Let's make an example:
IP address 192.168.0.1, subnet mask 255.255.255.0
This network will have these stats:
Network address : 192.168.0.0
Broadcast addresss : 192.168.0.255
Minimum Host address : 192.168.0.1
Maximum Host address : 192.168.0.254
Maximum hosts: 256
In this network you can ping from 192.168.0.1 to 192.168.0.254, but you CAN'T ping 192.168.1.1, because it's on a different network.
Now, IP address 192.168.0.1, subnet mask 255.255.254.0 (23bit subnet, 23 ones, 9 zeros)
This network will have these stats:
Network address : 192.168.0.0
Broadcast addresss : 192.168.1.255
Minimum Host address : 192.168.0.1
Maximum Host address : 192.168.1.254
Maximum hosts: 512
In this network you can ping from 192.168.0.1 to 192.168.1.254, but you CAN'T ping 192.168.2.1, because it's on a different network. See the difference? I now can have 500++ hosts in my new network, it's not limited to 192.168.0.254, I can go through 192.168.1.254.
Now I can keep on reducing the subnet mask bit and expand my network until I can fit my hosts into that network. No one can object that, IP addresses work like that.
Maybe I'll make a primer about IP addressing sometime...
zzz2496
Edit: crap, I forgot to explain something...
-
New #34
Yes, I believe this is solved.
I also edited the HOSTS file to include "192.168.10.200 Serv01" and will transition back to the "Serv01" notation on my mappings, and see how it goes.
You can modify the subnet mask anyway you want to determine the number of hosts you need. Originally I had the alternate IP address set to 192.168.0.1 255.255.0.0 so I could address everything in the 192.168.x.x range. This worked fine on the Windows 2000 machine, but intermittently failed in XP (just like it intermittently failed in W7), so it's probably not the 255.255.0.0 that was the issue, but the same Browser service issue.
I could probably do that with my single primary IP address of 192.168.10.244 with a mask of 255.255.0.0 and have access to every 192.168.x.x address and not need an alternate IP address. I intend to experiment with this in the W7 machine again.
-
-
-
New #37
Hi.
For years that I have this problem, and I already knew most of what was written in this thread.
I started to notice it the first time I needed to add a secondary IP address to a Windows 7 machine, and the same applies to Windows 8.
The fact is that the the solution given does not solve the problem, it's a just workaround.
In my scenario I have a Linux PDC SMB server (192.168.16.254) and I regularly need to configure customer's routers that often use IPs like 192.168.0.1, 192.168.1.254 and so on.
Normally I only notice that the network is failing after shutdown the client computer and when using it the next day, but I believe that if the resource server is not used for a few hours the problem will arise before, maybe some kind of timeout happens within the name resolution system.
What I will try today is to manually set the WinS server to the PDC server to see if works better that way, but I believe that this should be considered a Windows Network bug. The addition of a second IP address to the network interface shouldn't break the connectivity of the first IP address.
I will also test if the connectivity is only lost between the client and the PDC or if it also happens between the client and other network clients.
Thank you for reading...
-
New #38
Update about the tests I said I would do:
- The connection with other clients remains ok, only the connection to PDC fails;
- The WinS configuration don't work.
Any ideas I can test? That don't consist on adding non standard configurations like messing with the hosts file.
I would actually like to understand what happens when we add the second IP that causes this problem. The DNS, GW are exactly the same and this worked correctly on Windows XP (don't know about Vista, never used it).
Cya.
Quote
Related Discussions