Server cannot be accessed by a certain LAN IP

16-bit

16-bit

16-bit

Associate
Joined
16 Sep 2006
Posts
377
Location
In the vicinity
I've had this issue where any workstation that gets the IP of 192.168.7.149 cannot connect to our fileserver (192.168.7.3). Windows firewall is disabled with no third party in place, no funky routes or IPsec policies and I've checked the switch for any rules/errors but there's none. has anyone had this issue before?
 
I take it these are within the same /24 subnet? You've said there are no statics on the fileserver so that rules that out. Have you tried a tcpdump from the fileserver if it's a unix box?

Can you ping the fileserver from the .149 box?

From another machine on the same subnet, can you ping 192.168.7.149, and if you do an arp -a afterwards, does the mac address match up with the machine in question?

Normally this sort of problem is a dodgy arp entry on the gateway router but it sounds like you're on a flat network. Maybe duplicate IP, where the offending device doesn't respond to ICMP? Have a look at the router that holds the subnet's default gateway (if there is one) to see if the arp entry marries up?
 
Last edited:
Oops I left a fair bit of info out of that!

To answer some of the questions:
The fileserver is windows 2003 and the workstations I've tried are xp/7
It's indeed a flat network on the same subnet.
.149 is reserved in dhcp to another device which is using another IP(so it wouldn't allocate it to another device). I'll just exclude it from dchp.
Cannot ping or connect on any open ports either way.
 
You must log in or register to reply here.
Back
Top Bottom