Crazy SBS 2008 client ip address problem.

September 12, 2010 at 20:07:35
Specs: Windows 7
Sorry I couldn't be more discriptive in the subject but this is crazy. Windows 7 client has an ip address of, atleast that is what ipconfig returns. The server thinks it is even though wins shows the client as What the heck could cause this to happen? I can't use remote assistance because of this problem. If you ping the client name from the server, it tries to ping Now let me give the run down of the network setup. Main office has the server and every thing is on The office across the street is on address'. The pc's at the office across the street get their address' from a router and there is a vpn provided by the ISP that is always on, so I can ping back and forth and share folders no problem. I use wins to help with resolution. I noticed there was a problem when I found event id 10009 in the event viewer for the server. I had this event before on the server relating to all the pc's at the office across the street. I followed some instructions online and resolved this issue. It was a group policy/windows firewall issue. Now I'm getting the same problem but only with this one pc. One further note. This pc use to be at the main office and I moved her across the street.

See More: Crazy SBS 2008 client ip address problem.

Report •

September 13, 2010 at 05:53:52
I had something similar happen & the router was the cause. I had to remove it from the DHCP list iirc. What IP does the router think belongs to that computer name?

How do you know when a politician is lying? His mouth is moving.

Report •

September 13, 2010 at 07:58:56
Kinda surprised to read you have SBS and does not appear you are using its dhcp service which can also be configured to update DNS. I get this from the fact you say the server [DNS] sees the pc at x.x.x.15 though wins and the pc say x.x.x.8. Wins got updated but dns apparently did not.

You didn't tell us how the 192.x.x.x network is getting its ip.

It appears the moved pc is requesting and getting a ip from the 10.x.x.x subnet

In Active Directory /sites and services do you have the 10.x.x.x network listed? You should as a subnet so AD knows about it.

Are you doing ip reservations [mac address filtering] ? If yes this would explain why the moved pc got the ip it did. Otherwise you need to tell us a bit more about how you are handling dns and ip assignments

Report •

September 13, 2010 at 09:41:24
Ok thanks for the quick response. I am using DHCP on the sbs 2008 server at the main office. Using 192.168.1.X. The office across the street has a cisco router provided by the ISP using its own DHCP 10.0.1.X. This remote office also has a vpn to the main office that is always on. The pc's across the street have domain.local as a suffix, sbs 2008 as their dns address, and sbs 2008 server ip as the wins server address. You just made me think of something. Maybe this pc doesnt have the server as the dns address. I could have turned off dhcp on the router at the remote office and pointed the pc's at the remote office to use dhcp from the server across the vpn at the main office but I have read that this causes alot of network traffic and I wasn't 100% sure how to do it. I will now double check that the problem pc has the sbs 2008 server as its dns address. thanks

Report •

Related Solutions

September 13, 2010 at 11:19:32
Ok thanks for your help. It was the dns. The client was set to get dns from the dhcp server and since the dhcp comes from the router that is provided by the ISP and the dns provided by the router are the ip addresses to the isp dns, it couldnt register itself to the server. Its working fine now. I had read that when a server tries to find a client via machine name, it looks in dns first, then wins, then hosts file so I wonder why the server couldn't find the client anyway. If you have any thats on the last statement, I would appreciate it. Otherwise this issue is resolved. hmm I bet there was an old registration in dns for that client when it was at the main office and thats why the server was trying that wrong ip address and never made it to wins where the correct address was Thanks

Report •

Ask Question