PC set Internal Static IPs not seeing each other - no internet after hurricane - any suggestions
Hi. We are recovering from Irma and I have noted a strange issue on a few networks where their internet went down. The specific account I am concerned with is configured as following:
Netgear Router bridged to Comcast Modem - Router 192.168.16.1
2011 SBS Server - DNS, DHCP & AD - file sharing IP 192.168.16.2
I have configured the workstations to use the following configurations:
LAN IP (each PC has it's own) 192.168.16.10-16
Subnet: 255.255.255.0
Gateway: 192.168.16.1
DNS: 192.168.16.2
After setting this up on each PC, I still cannot connect to, nor ping the server or the other devices on the network.
They should be on a domain network, and they are definitely NOT home or Public at the least.
As this has happened on different networks, and the common link is they are Comcast and this has happened since we lost internet (it is popping in and out intermittently). I just need to get the workstations to talk to the server.
Any ideas or insights?
Netgear Router bridged to Comcast Modem - Router 192.168.16.1
2011 SBS Server - DNS, DHCP & AD - file sharing IP 192.168.16.2
I have configured the workstations to use the following configurations:
LAN IP (each PC has it's own) 192.168.16.10-16
Subnet: 255.255.255.0
Gateway: 192.168.16.1
DNS: 192.168.16.2
After setting this up on each PC, I still cannot connect to, nor ping the server or the other devices on the network.
They should be on a domain network, and they are definitely NOT home or Public at the least.
As this has happened on different networks, and the common link is they are Comcast and this has happened since we lost internet (it is popping in and out intermittently). I just need to get the workstations to talk to the server.
Any ideas or insights?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
PCs into switch connected to Netgear Router which is connected to the Comcast modem via the WAN/Internet port. I know it is networking 101, and setting the IP address of the PCs and server should allow for communication, but it is not. That is what is frustrating. Attached is a diagram of the current (and previously working, minus the Static IPs - it was DHCP on the workstations too, Server was always static). Am I just getting old or should that work internally?
It does not.
Network-Config.pdf
It does not.
Network-Config.pdf
ASKER
Kimputer - I will bring one down with me to test. I am heading down shortly. If it takes me a little while to get back to y'all, please bear with me as there is limited internet and cellular in that area now.
That's exactly the setup I wanted to verify that you had (plus it would let you fix any issues if you noticed something was off). As Kimputer pointed out, try replacing your switch. Another unlikely, but possible scenario, would be if somehow TCP/IP on the server was corrupted.
Please note, most switches suffering from sudden power outages, sometimes needs a few minutes of "rest" (fully disconnected from the power, really disconnect the power cable). While the LEDs might be blinking (therefore you thinking it's working properly), it won't work after powering off for a while.
ASKER
masnrock - that is what I am suspecting. What would be the quickest way to repair a corrupted CP stack?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
the switch takes a second or so to learn routes when powered on
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It was neither of the two other solutions, but it did resolve the issue.
You should be able to disconnect the Comcast modem from the Netgear and notice no impact internally, just to the outside world.