I have to Ping a server before I can connect

[coylert]

When I login to my workstation and try to vnc to a server on our new AD domain I have to ping the IP address first, then I can connect to the server, this is the case with browsing start run

Thanks,

 

[coylert]

Fixed I setup up a reverse lookup zone and configured primary DNS correctly

 

[coylert]

Now saying that I sovled might have been a bit premature as I had to use the IP address to get to the server this morning and not the name so Im still at a loss

 

[gmail2]

When you say you have to ping it - do you mean you have to ping it by hostname or by IP address? Also, are you VNCing to the server using hostname or IP address?

Irish Poetry - Karen O'Connor
Irish Poetry and Short Stories - Doghouse Books
Garten und Landschaftsbau

 

[coylert]

Thanks for the reply,

If I ping by host name it doesnt ping I have to ping IP then the host name will ping and then VNC will connect but its the same for start run \\servername

If I VNC with host name doesnt work but IP will.

 

[Helenp1983]

Maybe a WINS problem?

Is there an entry on your wins server for the server and does your PC look at the wins server?

 

[coylert]

No WINS is not setup as its its DNS on a AD Domain

 

[wdoellefeld]

Does the behaviour change if you use the FQDN to ping or connect?

(yay! shameless advertising. my side business)

http://www.frcp.net

 

[wdoellefeld]

I almost missed this. You stated this was trying to connect to a machine in a new domain... Sounds like a DNS suffix problem. Meaning your workstation might be appending the wrong domain. You can either add the new domain in the DNS tab of your TCP/IP connection properties or connect using the FQDN per my other post.

Of course that is all a moot point if your DNS doesn't have a zone on it for the new domain...

(yay! shameless advertising. my side business)

http://www.frcp.net