PC and network IP not the same

B

bxb7668

I have a Windows XP Pro box on a Windows Server 2003 SBS network. My problem
is the network thinks that the PC has a different IP address then the PC
actually has. On the PC, ipconfig tell me its IP address is 192.168.1.105.
When I look up that PC's name from the server (or from any other PC on the
network), the server thinks that its IP address is 192.168.1.35. It was
suggested that I do "ipconfig /registerdns" in the PC. This made no
difference. Any suggestions on how to resolve this?

Thank you
Brian
 
K

Kerry Brown

bxb7668 said:
I have a Windows XP Pro box on a Windows Server 2003 SBS network. My
problem is the network thinks that the PC has a different IP address
then the PC actually has. On the PC, ipconfig tell me its IP address
is 192.168.1.105. When I look up that PC's name from the server (or
from any other PC on the network), the server thinks that its IP
address is 192.168.1.35. It was suggested that I do "ipconfig
/registerdns" in the PC. This made no difference. Any suggestions on
how to resolve this?
Thank you
Brian

Have you set 192.168.1.105 as a static IP or are you using DHCP? At a cmd
prompt try "ipconfig /release" then reboot.

Kerry
 
R

Robert L [MS-MVP]

Assuming you have DNS or WINS on the server, check the records under DNS and WINS.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
I have a Windows XP Pro box on a Windows Server 2003 SBS network. My problem
is the network thinks that the PC has a different IP address then the PC
actually has. On the PC, ipconfig tell me its IP address is 192.168.1.105.
When I look up that PC's name from the server (or from any other PC on the
network), the server thinks that its IP address is 192.168.1.35. It was
suggested that I do "ipconfig /registerdns" in the PC. This made no
difference. Any suggestions on how to resolve this?

Thank you
Brian
 
L

Lanwench [MVP - Exchange]

bxb7668 said:
I have a Windows XP Pro box on a Windows Server 2003 SBS network. My
problem is the network thinks that the PC has a different IP address then
the PC actually has. On the PC, ipconfig tell me its IP address is
192.168.1.105. When I look up that PC's name from the server (or from any
other PC on the network), the server thinks that its IP address is
192.168.1.35. It was suggested that I do "ipconfig /registerdns" in the PC.
This made no difference. Any suggestions on how to resolve this?

Thank you
Brian
As mentioned, this is likely a DNS or WINS problem. You might post in
microsoft.public.windows.server.sbs - and mention more detail, such as DHCP
(in use? and if so, is the SBS box the DHCP server?), etc.
 
B

bxb7668

Kerry Brown said:
Have you set 192.168.1.105 as a static IP or are you using DHCP? At
a cmd prompt try "ipconfig /release" then reboot.
We are using DHCP. I'll try "ipconfig /release" this afternoon when I
next have access to the system. I'll also post to the
microsoft.public.windows.server.sbs group.
Brian
 
K

Kerry Brown

bxb7668 said:
We are using DHCP. I'll try "ipconfig /release" this afternoon when I
next have access to the system. I'll also post to the
microsoft.public.windows.server.sbs group.
Brian

It's unlikely to work but sometimes that procedure will force things. If it
doesn't work post the results of ipconfig /all

Kerry
 
R

Ron Lowe

You need to go to the DNS server and find the 'stale' record and delete it.

Then, on the XP box, ensure 'Register this connection in DNS' is checked,
on the DNS tab of the TCP/IP advanced properties.

Also, do an ipconfig /all on the XP box and ensure it is pointing to the
correct DNS server.

Then, do an ipconfig /registerdns on the XP box to force re-registration.

Then, F5 to refresh the DNS console on the server to see if it's picked up
the new A-record registration.
 
B

bxb7668

Thanks Ron. I'm the untrained SA for my church where this is
happening. I can log onto the server. How do I find the stale record
and delete it? The rest of the instructions I understand.

Thank you
Brian
 
K

Kerry Brown

When logged onto the server click on start then administrative tools then
dns. If administrative tools is not in the start menu then look in the
Control panel. You can also goto Start then run and type "dnsmgmt.msc". I
believe it is also in the server management console on SBS 2003.

Once you have the DNS console open expand the forward lookup zones then look
in the records for your domain name. When you find your computer name if it
has the wrong IP listed then right click it and delete it. If you have
Reverse zones implemented you will have to do the same thing there. Expand
the reverse zones then look for your subnet. It will be something like
1.168.192.in-addr.arpa Look for your computer name. If it is using 35 then
delete it. Be very careful editing DNS. If you are not sure ask.

Kerry
 
K

Kerry Brown

I just checked on a SBS 2003 server and it is not in the Server mangement
console but any of the other methods of starting the DNS console will work.

Kerry
 
B

bxb7668

Thank you Kerry. That was the problem. Once I remove the stale DNS
entry and re-registered the client, it connected successfully.

Brian
 
K

Kerry Brown

Your welcome.

Kerry
Thank you Kerry. That was the problem. Once I remove the stale DNS
entry and re-registered the client, it connected successfully.

Brian
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top