Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Users of our accounting server have a couple of times gotten odd errors about communication and unable to access SQL resources. When it happens it happens to all of our users at once. My first thought was maybe the SQL Server is out of whack but event logs for it look fine and no issues with the maintenance tasks that are scheduled.

The server does appear to be seeing an IP address conflict however at intermittent times that seem fairly close to the incidents. The MAC address is one of our laptops. All of our equipment excepting the usual stuff is DHCP, double checked and the server address is on the exception list so it should not be handing out at all. I've seen it where our VPN users had trouble because their LAN was on the same range as our LAN and their router wouldn't let them access our network because it thought everything was local but never the other way around. Has anybody ever seen this behavior where a remote LAN gave interference with the Local LAN?

share|improve this question
    
"our VPN users had trouble because their LAN was on the same range as our LAN" - WTF? No wonder you've got problems. Yes, its just possible to build a working network like this - but a really stupid idea. Even if that's not the cause of this problem, you need to sort it out. –  symcbean Dec 20 '10 at 16:42
    
Our internal network is on 192.168.1.0/24, a lot of home network devices sit on 192.168.1.0/24 like netgear and Linksys routers. When they try to go to a server sitting on say 192.168.1.20 it tries its own local area connection since it is on its own range. This is not the issue here and I think your missing my question. –  Shial Dec 20 '10 at 17:25

1 Answer 1

We have had problems previously with a VPN, where if a remote users IP range was set to the same as ours (192.168.0.x) then it would try and route traffic over their local router, rather than using the vpn. Soon as they changed this to a different range, then all traffic went over the vpn correctly.

share|improve this answer
    
I've had that too, what I'm seeing here seems like somehow our internal network seemed to somehow see a remote users ip range and tried to route to it leading to a reported IP conflict (At least this is the only explanation I can come up with) –  Shial Dec 20 '10 at 17:28

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.