Limited connection to server until change of IP address

[brockj]

So I have been trouble shooting this issue, and I think I made a new discovery. Basically we are having issues with client machines connecting a certain server, however if I change the IP address of the machine everything works fine. Any thoughts? I have seen this before, but I have no idea how to fix the issue.

 

[DaiShan]

We need a TON more information to help you solve this problem. Which OS on the server/clients? What TYPE of server (apache, file server, or is it not responding to pings) how are you trying to access it? (by ip address, or host name?) How are IP addresses assigned in your network (all static or all dhcp?) Are you sure there isn't an IP address conflict on your network? (are you mixing dhcp and staticly assigned addresses?) Try to choose one or the other, alternatively you can set statically assigned IP addresses by MAC on your DHCP server...

 

[brockj]

sorry, this is in relation to another post where we thought the issue was T1 based. Machines are all XP Pro server are 2003, I always able to ping the server; however I am unable to establish a remote desktop, search shares or connect with outlook client.

Basically from their DHCP assigned address when they are running on our backup line everything is fine, if we switch the line over to our T1 then about half of the machines are unable to connect to the exchange server for browsing, outlook, ect. ALthough the machine will still be able to ping the server. But, if I change the IP address of the machine to a static IP then everything works fine. I am thinking this could be more a server issue, however I have no idea where to go on this.

 

[DaiShan]

are you trying to access the shares by hostname? Also you NEED to have your server on a STATIC IP address. if you are attempting to access by hostname are you updating the DNS information? Here is a quick test to determine if that is your problem: on the server after you switch IP addresses run ipconfig and grab the current IP address. Then on one of the client PC's go to start then run and type \\<ip address of server> If it brings up a list of shares then that means it is a DNS issue and you can begin trouble-shooting there. Additionally, remember that you can flush your DNS cache on your xp client machines by running the command ipconfig /flushdns this will keep your client machines from looking for the server in the wrong place. You may also want to look at how Nat'ing/firewall is being handled if you are using either of those services on your router.

 

[brockj]

DNS resolution is not the issue, when I ping the server name, I get the response with the proper IP address. I have pretty much essentially ruled out a DNS issue.

What is wierd is that I can make the change in the router to only see the one connection to our corporate office and everything will work, when I switch over to the Point to Point T1 the issue's begin. I have restarted the machines and done basic troubleshooting on the local workstation but the only thing that seems to make a difference is when I change the IP on the workstation.

 

[DaiShan]

I'm not saying that DNS is the issue, but you definitely have NOT ruled it out. If I set an A record for superman.domain.com in my dns zones to point to 67.18.255.117 for example and bring another host up on that IP I will still receive pings from superman.domain.com just fine, but it is not coming from the correct server. Are you sure that your workstations can route to the new IP address? Try running in a cmd prompt "route print" and see if there is a route to your new network segment. If your clients are 192.168.1.xxx and your servers are 10.0.0.xxx you either need to add a static route on your router or on the clients.


/edit probably not a routing issue, I'd still check the IP address on the server, without knowing more about your specific set up that's my best guess.

 

[spidey07]

Sounds like a DNS problem in all honesty. Just because you get name resolution doesn't mean your DNS is good.

Something is going on with DNS, computer/name registration. Every problem you listed means your active directory and DNS is fubarred.

1) What DNS server are the clients using?
2) Is this remote subnet defined in AD sites and services?

 

[brockj]

Ok, I will do my best with this as I am not a AD guru...

The location is listed in AD Sites and services, and if I do a rt click/properties on the location the subnet is listed.

For the machines the primary domain controller (which also happens to be exchange) is the DNS server. I know this is not an ideal setup and will be changing this shortly, however until I cand get the funds for a new server for exchange this is what I am stuck with.

As far as the routes I can get to other devices in the remote subnet, just not one particular machine (exchange)