This problem is a little tough to explain, but I'll try. I'd like to find if there is a resolution for it.
The way our company network is set up, we log into a domain. This gives me access to a number of network resources.
As a programmer of embedded equipment, one of the devices I've created can communicate via Ethernet to host systems.
Our network was originally laid out as a 253 system segment at 192.168.10.x (mask of 255.255.255.0) and this network segment has no free space for me to add a number of these controllers onto it since it's filled up almost to it's entirety with systems and servers.
So, I've set these units as addresses in 192.168.0.x, and I've created an alternate IP address on my system as 192.168.0.250, with a mask of 255.255.255.0.
This works, as the IP stack knows which address to send requests out to. If I address something in the 0.x range, the system originates at 0.250, anything else goes out as 10.x. The problem is, my network resources on the domain disappear occasionally, and when I delete the alternate IP address, they come back. I've been using this scheme for quite some time on Windows 2000, and it was never a problem, so something has changed over the years. It seems to work for a while, and then randomly the resources drop out.
Does anyone know why doing this would cause the connection to network resources to just vanish? It would seem that what m doing should work, since it does work. I just need to find the "irritant" that causes the connections to be lost.
Before you suggest we expand our network to support more hosts on the subnet, our IT department has rejected this. They don't want to have to go to every machine in the network (multiple buildings), reset subnet masks on clients and servers, and hope "it all works" after that.
The way our company network is set up, we log into a domain. This gives me access to a number of network resources.
As a programmer of embedded equipment, one of the devices I've created can communicate via Ethernet to host systems.
Our network was originally laid out as a 253 system segment at 192.168.10.x (mask of 255.255.255.0) and this network segment has no free space for me to add a number of these controllers onto it since it's filled up almost to it's entirety with systems and servers.
So, I've set these units as addresses in 192.168.0.x, and I've created an alternate IP address on my system as 192.168.0.250, with a mask of 255.255.255.0.
This works, as the IP stack knows which address to send requests out to. If I address something in the 0.x range, the system originates at 0.250, anything else goes out as 10.x. The problem is, my network resources on the domain disappear occasionally, and when I delete the alternate IP address, they come back. I've been using this scheme for quite some time on Windows 2000, and it was never a problem, so something has changed over the years. It seems to work for a while, and then randomly the resources drop out.
Does anyone know why doing this would cause the connection to network resources to just vanish? It would seem that what m doing should work, since it does work. I just need to find the "irritant" that causes the connections to be lost.
Before you suggest we expand our network to support more hosts on the subnet, our IT department has rejected this. They don't want to have to go to every machine in the network (multiple buildings), reset subnet masks on clients and servers, and hope "it all works" after that.
My Computer
At a glance
Win 7 x64 ProfessionalIntel Core i5-750 2.67Ghz4gbNvidia GeForce 9500GT 512mb
- Computer Manufacturer/Model Number
- DYI
- OS
- Win 7 x64 Professional
- CPU
- Intel Core i5-750 2.67Ghz
- Motherboard
- Gigabyte P55M-UD4
- Memory
- 4gb
- Graphics Card(s)
- Nvidia GeForce 9500GT 512mb
- Sound Card
- On MB
- Monitor(s) Displays
- Lg Flatron
- Screen Resolution
- 1280 x 1024
- Hard Drives
- C: 200mb Maxtor SATA 3
D: 500gb WD SATA 3
)