DNS / Pinging Issues

[Joe Schmoe]

Your assistance in this matter would be greatly
appreciated:

I implemented a new manageable switch at with an ip
address of 202.1.1.250.

I have (3) workstations with the following names / ip
addresses:

PC1 - 202.1.1.172
PC2 - 202.1.1.188

The problem is that I cannot ping 202.1.1.172 from any
workstation in our network. I have performed the
following actions to alleviate the problem:

1) Configured a static address of 202.1.1.172 - No Success.

2) I erased the DNS Entry and PC1 from the DOMAIN. Then I
added PC1 back to the domain and DNS was dynamically
updated but I still cannot PC1 from any PC on our network.

3) When I use the Ping Command: "ping PC1", pinging fails
but the IP address is listed in the brackets (202.1.1.172).

4) When I ping the IP address of PC1 by using the
following command "ping 202.1.1.172", ping also fails.

I do not think that the new switch installation has
caused this issue as I need the ability to ping PC1 from
any PC on the network. Please advise.

 

[Ace Fekay [MVP]]

In

Your assistance in this matter would be greatly
appreciated:

I implemented a new manageable switch at with an ip
address of 202.1.1.250.

I have (3) workstations with the following names / ip
addresses:

PC1 - 202.1.1.172
PC2 - 202.1.1.188

The problem is that I cannot ping 202.1.1.172 from any
workstation in our network. I have performed the
following actions to alleviate the problem:

1) Configured a static address of 202.1.1.172 - No Success.

2) I erased the DNS Entry and PC1 from the DOMAIN. Then I
added PC1 back to the domain and DNS was dynamically
updated but I still cannot PC1 from any PC on our network.

3) When I use the Ping Command: "ping PC1", pinging fails
but the IP address is listed in the brackets (202.1.1.172).

4) When I ping the IP address of PC1 by using the
following command "ping 202.1.1.172", ping also fails.

I do not think that the new switch installation has
caused this issue as I need the ability to ping PC1 from
any PC on the network. Please advise.

Since no pings (by name or IP) returns an answer, the only thing I can think
of if you implemented VLANS or have some sort of personal firewall on the PC
or the subnet mask is incorrect on the PC.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Deji Akomolafe]

yeah, this is not DNS.

Try tracert 202.1.1.172 and see where the packet is gone and where it dies.
Alos, you ommited to say anything about PC2 (202.1.1.188). Does that reply
to ping?

In any case, IF you can't ping by IP, don't look at DNS.

--
Sincerely,

Dèjì Akómöláfé, MCSE MCSA MCP+I
www.akomolafe.com
www.iyaburo.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon
"Ace Fekay [MVP]"

 

[Joe S.]

Hello:

I tried tracert to "202.1.1.172" and I get "Request
timed out along with the hops". I can successfully ping
and tracert works for 202.1.1.188. Any further advice
would be helpful.

 

[Deji Akomolafe]

WHERE did it start to time out. THAT is where your problem lies. Is it
timing out at the router/switch? Did it get to the computer and time out
from there? If it got to the computer, then you may be looking at either a
bad NIC or a misconfigured Default Gateway entry, especially since you said
the other computer on the same subnet is working. It could also be a bad
TCP/IP stack. I would say, replace the NIC and reconfigure TCP/IP.

In any case, try the networking newsgroup. This is not DNS.

--
Sincerely,

Dèjì Akómöláfé, MCSE MCSA MCP+I
www.akomolafe.com
www.iyaburo.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon
Hello:

I tried tracert to "202.1.1.172" and I get "Request
timed out along with the hops". I can successfully ping
and tracert works for 202.1.1.188. Any further advice
would be helpful.

 

[Ace Fekay [MVP]]

Hello:

I tried tracert to "202.1.1.172" and I get "Request
timed out along with the hops". I can successfully ping
and tracert works for 202.1.1.188. Any further advice
would be helpful.

As Deji said, this is not really a DNS issue but rather a nertworking issue.

But since we've already started, can we see an ipconfig /all from both
machines and one of your DCs please?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Ace Fekay [MVP]]

In

Hello:

I tried tracert to "202.1.1.172" and I get "Request
timed out along with the hops". I can successfully ping
and tracert works for 202.1.1.188. Any further advice
would be helpful.

Can the machine in question ping another machine on the same subnet?


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory