Can't ping domain name

[plexer]

Ok this is weird I've got a brand new win 7 ent laptop only recently setup in the workshop at the moment.

 

If I do an nslookup on the domain name wayland.local it gives me the correct 2 ip addresses for the DC's.

 

If I ping wayland.local it tells me it can't find it.

 

If I remove the machine from the domain it can ping wayland.local fine.

 

I've tried other machines on the domain and they can ping wayland.local fine.

 

This machine also won't apply group policy because of this.

 

The 2 adservers both pass all dcdiag tests fine.

 

Ben

[sonofsanta]

I'd be suspicious of the windows firewall & the domain profile.

 

It may be related to this kb: Event ID 5719 and event ID 1129 may be logged when a non-Microsoft DHCP Relay Agent is used (as first discussed in this thread on here)

[plexer]

I dunno I've setup loads of these same model laptops and not had this issue before also it's not a domain wide issue as I just applied a gpo to a computer in one of the labs and that picked it up fine and that machine is connected to the same switch as this troublesome laptop.

 

Think I'm going to re-deploy the os and see.

 

Ben

[chazzy2501]

can it ping the ipv4 addresses of the DCs? Maybe it's trying an ipv6 ping..

[laserblazer]

I had a similar issue and that was down to the firewall on the client. Check the services to make sure it has started.

[plexer]

Firewall service is fine, re-installed OS exactly the same issue, grrr.

 

Ben

[free780]

Do u push out dns server settings via gpo. I dont think its supported on anything after xp.

[plexer]

Nope dns are scope options in DHCP.

 

I can resolve wayland.local using nslookup on the affected machine and it gives me the correct ip's but cannot ping the domain name or connect to shares via unc uses hostnames.

 

Ben

[sonofsanta]

Network driver update?

[plexer]

Can give it a go but it can ping the domain name fine until I add it to the domain if I disjoin it it works fine.

 

Ben

[sonofsanta]

Disabling the firewall has no effect, I take it? Obviously not a solution but could be a clue. I know I'm teaching grandma to suck eggs with this, but it really sounds like the domain profile being a PITA where the public profile is ok, or some shenanigans with the firewall profiles (as mentioned in the linked thread earlier).

[plexer]

Stopping the firewall service doesn't help.

 

Ben

[sonofsanta]

Static IP instead of dynamic? /clutching at straws

[plexer]

Nope tried a static with only one dns server still nothing, rebuilt machine and back to a dynamic but still no dice if it was a major issue I'd expect to be getting reports from others users of problems but it's doing my swede in now.

 

Ben

[plexer]

Right narrowed down the issue it's something to do with my directaccess group policy the machine was a member of that group as that's why I had it in to setup so my current theory is that once it's applied the direct access settings even though it's internal on the network for some reason directaccess is running but doesn't have a connection which is why the ping etc.... is failing.

 

Now to work out why.

 

Ben

[bart21]

If the client can not reach the network location server it will think it is external to the LAn and direct access will connect