Unsolved
This post is more than 5 years old
6 Posts
0
21608
June 17th, 2014 08:00
Weired Connection Problem
Hi Everyone!
I have an Office Network that consists of:
Netgear Prosafe VPN Router w/ IP Addr: 192.168.1.1
Dell PowerConnect 2842 Managed Switch (In managed mode - no VLAN assigned - only used it for the basic switch function and Link Aggregation for my FreeNAS file server) w/ IP Addr: 192.168.1.2
FreeNAS Server (Self Build w/ 4 Intel NIC in Link Aggregation Mode) w/ IP Addr: 192.168.1.80
and about 10 PCs (192.168.1.100 - 110)
One of the PC 192.168.1.108 all of a sudden cannot "Map" a network drive on the FreeNAS server in windows and can't ping it either, but can ping and Map networks shares on other PCs on the same network! I switched out the CAT5e cable that's connected to the in wall jack, and it is the same thing - I even ran a pre-made CAT6 cable directly to the switch - same thing! Try pinging 192.168.1.108 from the FreeNAS's console is unpingable (all TCP/IP Packet lost) All other PC (except 192.168.1.108) can connect and Map a network drive to the FreeNAS server! Pls help in troubleshooting. TIA!
PS. All Network devices are on the 255.255.255.0 subnet each with its own static IP address w/ a gateway of 192.168.1.2 and 192.168.1.1
SGI
6 Posts
0
June 17th, 2014 08:00
Update: the Netgear's web based diagnostic tool can ping the FreeNAS Server but could not ping the PC w/ IP 192.168.1.108. I also just changed the IP address from 192.168.1.108 to 192.168.1.8 and it can sucessfully ping and map the network drive!
SGI
6 Posts
0
June 17th, 2014 14:00
No other devices uses the 108 address. (checked each machine physically and do a network scan) DHCP leases range (for wireless devices) does not include 108 address as well.
SGI
6 Posts
0
June 17th, 2014 14:00
the 192.168.1.8 was unpingable after a few minutes (but can still connect to the network share!!!)