Blockchain technology has already revolutionized finance thanks to Bitcoin. Now it's disrupting other areas, including the realm of data protection. Learn how blockchain is now being used to authenticate backup files and keep them safe from hackers.
COURSE of the MONTH
13 days, 18 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Why isnt my equipment communicating with our DC
Posted on 2011-03-07
I have a CNC Mill that is networked in order to gain access to a file folder share. Out of nowhere I can not connect to this file share with the account credentials from that machine. Permissions havent changed, Account isnt locked out. I can use the same credentials at a computer and log in just fine. What is interesting though is I can not ping our DC from that machine. I can ping other pieces of equipment but not our DC. I have only removed print drivers and printers from the DC this weekend. Nothing else that would effect it to my knowledge. I am running server 2008 64bit.
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
12
7
5
24 Comments
is dc and cnc mill on same subnet and vlan?
looks like connectivity problem - maybe some kind of firewall - or blocked ports on router
Jan MA CCNA
looks like connectivity problem - maybe some kind of firewall - or blocked ports on router
Jan MA CCNA
When you ping the DC from that machine are you pinding the IP or the DC name?
Is that machine using static IP or DHCP?
Is that machine using static IP or DHCP?
can you tracert from dc to cnc .
do arp-a tocheck if you mac is right one
if not arp -d (delete cached macs) and
ipconfig /flashdns
do arp-a tocheck if you mac is right one
if not arp -d (delete cached macs) and
ipconfig /flashdns
When you ping the DC name from the machine, does it convert it to the IP address of the DC before it starts to attempt to ping?
ok well now I am getting an echo request when I ping IP but when I ping DC name it says can not resolve. Still can not log in. Tried credentials on a computer and no problems logging in no problems accessing folder share.
It appears that you have a DNS issue. If you ping the DC'c name and it cannot resolve, DNS is the issue. Run the IPCONFIG /ALL from a command prompt and look at what the machine has for its' DNS server. Is the DC in question also the DHCP server?
yes DC is DHCP also. When I do the IPconfig it says no DHCP available...if that were true we would be having problems all day long with the everything. right?
The DHCP server leases its' addresses for a certain number of days, if DHCP just quit you may not see issues until those leases run out and new ones cannot be given.
Go to a non essential PC that is working and type IPCONFIG /RELEASE then IPCONFIG /RENEW and see if it can retrieve a new lease.
Go to a non essential PC that is working and type IPCONFIG /RELEASE then IPCONFIG /RENEW and see if it can retrieve a new lease.
The first several attempts for the renew it said destination host unavailable. Then it finally renewed
Also, at the CNC i was trying to ping again. (Actually 2 CNC machines doing the same thing) at first no response try pinging again and I get a response. It seems intermittent.
Sounds like DHCP and or DNS are having issues.
You can try restarting those services on the server.
Are bot PCs going through the same switch? You have have network hardware issues.
You can try restarting those services on the server.
Are bot PCs going through the same switch? You have have network hardware issues.
Both CNC moved to different switch (just for troubleshooting sake) Cisco switch lights blinking away. Restarted DNS and DHCP services. Still no luck. I noticed when I boot CNC there is a message that says cannot find LMHOSTS in the DOS boot screen right after it tries to initialize tcp/ip DHCP
Featured Post
Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
Resolving an irritating Remote Desktop connection that stops your saved credentials from being used.
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses
Course of the Month13 days, 18 hours left to enroll
801 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.