I was recently hired at a small company and they've never had a tech specialist before, and to be honest, having just graduated college, I've never held the position before so we both have a lot of catching up to do. What I'm doing right now is this:
I have a comcast business gateway, and it operates on the 10.1.10 subnet and doesn't have a wireless capability. Why Comcast decided that was a good idea is beyond me, and also beyond the point.
I have a D-link 524 wireless router connected to said business gateway. It operates on the 192.168.0 subnet.
For the most part interoffice connectivity is fine. I have 6-8 machines, including my desktop that operate on the wireless which means they are in 192.168.0. I have a host of IP camera's attatched to the D-link through a PoE switch, all operating on the 192.168.0. I have a sunfire server (an old Sun Microsystems ProductO) running server 2k3 on the 192.168.0. I have a single virtual machine though a Pivot3 server (which is a linux based system) running on the 10.1.10. All of these can connect with each other via remote desktop, vnc, and can all connect to the internet through the business gateway.
Here's my problem. I feel that a proper work place, especially one of this size doesn't need to subnets, and the people I work for agree. So I took the second of my virtual machines resting on the Pivot3 server, running server 2k3, essentially a twin to the one above. It was originally on the 10.1.10 and was connecting without issue. I unplugged it from the business gateway(10.1.10) and plugged it into the D-link(192.168.0). All of the machines are set to DHCP and the problem machine picked up its new address just fine, I could tell from the DHCP settings on the D-link. I remote connected to it without an issue. It won't connect to the internet. I started pinging to see where it would connect to. It time-outs on all pings that aren't loopback. It won't ping the D-link, which is its default gateway. The only thing I could think was maybe firewall settings, so I opened them up and created a giant chasm for it, allowing literally anything to access it and it to access anything. Still won't register pings, from anywhere. When I ping it from outside sources it responds as normal.
Long story short I have a pair of Identical server2k3 virtual machine inside of a Pivot3 box which itself runs linux. They connect to the comcast business gateway(10.1.10) with out issue, but while connected to the D-link, they refuse to establish connections to anything. They can receive ping and remote desktop though.
Also I did try to change the subnets on each router independently, to no avail. My best guess is that the issue is somehow rising from the fact that the pivot3 is running windows inside of linux, but it only happens with the D-Link router.
I apologize for the length, I wanted to present all the facts as best I could
I have a comcast business gateway, and it operates on the 10.1.10 subnet and doesn't have a wireless capability. Why Comcast decided that was a good idea is beyond me, and also beyond the point.
I have a D-link 524 wireless router connected to said business gateway. It operates on the 192.168.0 subnet.
For the most part interoffice connectivity is fine. I have 6-8 machines, including my desktop that operate on the wireless which means they are in 192.168.0. I have a host of IP camera's attatched to the D-link through a PoE switch, all operating on the 192.168.0. I have a sunfire server (an old Sun Microsystems ProductO) running server 2k3 on the 192.168.0. I have a single virtual machine though a Pivot3 server (which is a linux based system) running on the 10.1.10. All of these can connect with each other via remote desktop, vnc, and can all connect to the internet through the business gateway.
Here's my problem. I feel that a proper work place, especially one of this size doesn't need to subnets, and the people I work for agree. So I took the second of my virtual machines resting on the Pivot3 server, running server 2k3, essentially a twin to the one above. It was originally on the 10.1.10 and was connecting without issue. I unplugged it from the business gateway(10.1.10) and plugged it into the D-link(192.168.0). All of the machines are set to DHCP and the problem machine picked up its new address just fine, I could tell from the DHCP settings on the D-link. I remote connected to it without an issue. It won't connect to the internet. I started pinging to see where it would connect to. It time-outs on all pings that aren't loopback. It won't ping the D-link, which is its default gateway. The only thing I could think was maybe firewall settings, so I opened them up and created a giant chasm for it, allowing literally anything to access it and it to access anything. Still won't register pings, from anywhere. When I ping it from outside sources it responds as normal.
Long story short I have a pair of Identical server2k3 virtual machine inside of a Pivot3 box which itself runs linux. They connect to the comcast business gateway(10.1.10) with out issue, but while connected to the D-link, they refuse to establish connections to anything. They can receive ping and remote desktop though.
Also I did try to change the subnets on each router independently, to no avail. My best guess is that the issue is somehow rising from the fact that the pivot3 is running windows inside of linux, but it only happens with the D-Link router.
I apologize for the length, I wanted to present all the facts as best I could