Naerwen
asked on
Can ping out and resolve but can't get to the server. Help.
All,
I have a strange problem. This weekend I came in and recabled the 10 servers in our domain. This was because I found intermitent connectivity issues with my DC. After researching the problem I looked at the cabling and noticed that the sheath was pulled back and that several wires had shiners on the inside the rj45 clip. I made up the new cables and tested them one by one as I put them in. All passed and all seemed to work well.
However, my File-Server <actual name>, is not reachable over the network. Though, I can ping and nbtstat -s anything I want while logged in. We used cached credentials so I am able to login as myself. I have looked into the event log and found ....
event Id: 60 Source:WinMgmt
WMI ADAP was unable to process the performance libraries: 0x80041001
and
event Id: 4097 Source: EventSystem
The COM+ Event System deteced a bad return code during its internal processing. HRESULT was 800706B9 from line 42 of . \eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.
beyond this two errors I see ...
event id: 2504 which denotes that the server can not bind to the transport of device ..... device\NetBT_Tcpip_{F7BCBD
... I am at a loss and not sure how to proceed.
- nbtstat -a <servername or ip> works like a champ on the rest of the servers[@ 10] and workstations[@ 50]
- nslookup works fine ... on the same as above.
- ping works OUT of the server to the other servers and workstations on the network.
- The server resolves Internet requests but does not load the page. That is, you can see the IP address in the bottom left corner of IE(6).
Please let me know if there are any other data the may be required to help me with this issue.
Thank you,
Naerwen
I have a strange problem. This weekend I came in and recabled the 10 servers in our domain. This was because I found intermitent connectivity issues with my DC. After researching the problem I looked at the cabling and noticed that the sheath was pulled back and that several wires had shiners on the inside the rj45 clip. I made up the new cables and tested them one by one as I put them in. All passed and all seemed to work well.
However, my File-Server <actual name>, is not reachable over the network. Though, I can ping and nbtstat -s anything I want while logged in. We used cached credentials so I am able to login as myself. I have looked into the event log and found ....
event Id: 60 Source:WinMgmt
WMI ADAP was unable to process the performance libraries: 0x80041001
and
event Id: 4097 Source: EventSystem
The COM+ Event System deteced a bad return code during its internal processing. HRESULT was 800706B9 from line 42 of . \eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.
beyond this two errors I see ...
event id: 2504 which denotes that the server can not bind to the transport of device ..... device\NetBT_Tcpip_{F7BCBD
... I am at a loss and not sure how to proceed.
- nbtstat -a <servername or ip> works like a champ on the rest of the servers[@ 10] and workstations[@ 50]
- nslookup works fine ... on the same as above.
- ping works OUT of the server to the other servers and workstations on the network.
- The server resolves Internet requests but does not load the page. That is, you can see the IP address in the bottom left corner of IE(6).
Please let me know if there are any other data the may be required to help me with this issue.
Thank you,
Naerwen
Are you using your file sever for routing as well?
ASKER
Lafflin,
No. This server is dedicated to file serving only. There is only about 100gb of data between 8 or so shared folders. It's all CAD data that needs to be accessed daily.
I must say it's odd. This server has not had a single issue in 6 months.
Naerwen.
No. This server is dedicated to file serving only. There is only about 100gb of data between 8 or so shared folders. It's all CAD data that needs to be accessed daily.
I must say it's odd. This server has not had a single issue in 6 months.
Naerwen.
Given your previous symptoms and issues, I would suspect the cabling - if nothing else changed.
I would try to get a hold of a factory cable and plug it into test it, or move the server to a known good working connection and plug it in there. Or if you have a cable tester on you, then use that - but check the cable. I'm a network guy, so I troubleshoot going up the OSI model. Always check the cabling.
You MIGHT have a half good termination - where small things can get through but there might be corruption on larger frames.
Are you able to get into network switches and look at the interface to examine errors?
PC
I would try to get a hold of a factory cable and plug it into test it, or move the server to a known good working connection and plug it in there. Or if you have a cable tester on you, then use that - but check the cable. I'm a network guy, so I troubleshoot going up the OSI model. Always check the cabling.
You MIGHT have a half good termination - where small things can get through but there might be corruption on larger frames.
Are you able to get into network switches and look at the interface to examine errors?
PC
ASKER
Pseudocyber,
I was testing a factory cable while composing this. I did not want to report on my findings until I was done. The results are the same no matter what cable I use. Both cables have been tested.
Regarding my switch configuration. I have a Dell Power Connect 5448. I have HTTP access and all ports are hard configed to 100/full to avoid auto-neg to 1gb. we have a mixed environment and the systems with 100mb full capability out weighs the ones with 1gb/full. Also, STP is set to disable.
Honestly, I don't know where to look to find errors on this switch. Never seen it before I got here. It seems Cisco-ish ... but I have not explored it.
Naerwen
I was testing a factory cable while composing this. I did not want to report on my findings until I was done. The results are the same no matter what cable I use. Both cables have been tested.
Regarding my switch configuration. I have a Dell Power Connect 5448. I have HTTP access and all ports are hard configed to 100/full to avoid auto-neg to 1gb. we have a mixed environment and the systems with 100mb full capability out weighs the ones with 1gb/full. Also, STP is set to disable.
Honestly, I don't know where to look to find errors on this switch. Never seen it before I got here. It seems Cisco-ish ... but I have not explored it.
Naerwen
whenever you see something like that it's not going to be a cable issue. If it was a layer 1 issue you wouldn't be pinging well. Ping -t can be used as a continuous ping to see if packets are dropping.
The reason I asked if this file server is routing is because you mentioned that it can resolve internet addresses.
So, to summarize, <file server> can ping other hosts, by name and IP address?
When you ping <file server> are you doing so by Name or IP? When you ping <file server> by name look at the IP the ping gives you and compare it to the actual IP <file server> is using.
Also, have you bounced the server?
The reason I asked if this file server is routing is because you mentioned that it can resolve internet addresses.
So, to summarize, <file server> can ping other hosts, by name and IP address?
When you ping <file server> are you doing so by Name or IP? When you ping <file server> by name look at the IP the ping gives you and compare it to the actual IP <file server> is using.
Also, have you bounced the server?
Dude, it's not the switch or the cable. Be careful not to always assume that the guy offering you free advice knows what he's talking about, that's sometimes not the case.
ASKER
Lafflin,
<<<whenever you see something like that it's not going to be a cable issue. If it was a layer 1 issue you wouldn't be pinging well. Ping -t can be used as a continuous ping to see if packets are dropping.>>>
The reason I asked if this file server is routing is because you mentioned that it can resolve internet addresses. <=== So sorry, I meant from Internet explorer the server can reach the Internet IP address of web sites ... however, it does not load the page. Looks like a dns problem but if www.yahoo.com resovles to xx.xx.xx.xx then I know that my DNS forwarders are working.
So, to summarize, <file server> can ping other hosts, by name and IP address? << Correct.
When you ping <file server> are you doing so by Name or IP? When you ping <file server> by name look at the IP the ping gives you and compare it to the actual IP <file server> is using.<<<< The server has static IP addressing. And the A and PTR records are present in DNS. Here are the results of my ping tests ...
C:\Documents and Settings\begas>ping file-server
Pinging file-server.craftechind.lo
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.10:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Documents and Settings\begas>ping 192.168.1.10
Pinging 192.168.1.10 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.10:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Also, have you bounced the server?<<< Yes many times.
Naerwen
<<<whenever you see something like that it's not going to be a cable issue. If it was a layer 1 issue you wouldn't be pinging well. Ping -t can be used as a continuous ping to see if packets are dropping.>>>
The reason I asked if this file server is routing is because you mentioned that it can resolve internet addresses. <=== So sorry, I meant from Internet explorer the server can reach the Internet IP address of web sites ... however, it does not load the page. Looks like a dns problem but if www.yahoo.com resovles to xx.xx.xx.xx then I know that my DNS forwarders are working.
So, to summarize, <file server> can ping other hosts, by name and IP address? << Correct.
When you ping <file server> are you doing so by Name or IP? When you ping <file server> by name look at the IP the ping gives you and compare it to the actual IP <file server> is using.<<<< The server has static IP addressing. And the A and PTR records are present in DNS. Here are the results of my ping tests ...
C:\Documents and Settings\begas>ping file-server
Pinging file-server.craftechind.lo
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.10:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Documents and Settings\begas>ping 192.168.1.10
Pinging 192.168.1.10 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.10:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Also, have you bounced the server?<<< Yes many times.
Naerwen
I'm not sure what to say, I was thinking that perhaps DNS was resolving to a static address that wasn't being used, I was going to say perhaps trying flush dns, but obviously that's not your issue, I have no idea.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
If the moderator wants ... I have no objection to assigning partial points to Lafflin... He made every effort to help. I just closed the question to fast .. sorry.
So, what was the problem?
ASKER
The problem was that Symantec Anti-virus locked all inbound communication because our switch was reset and lost settings during a storm. Some random activity during that incident caused symantec to close access to all inbound traffic.
While removing and readding the system to the Domain was NOT Necessary, simply removing the teefer 2 driver component was.
This is the second time I have had to post this. I would appriciate it if the Moderator would not remove my comments in the future.
Naerwen.
While removing and readding the system to the Domain was NOT Necessary, simply removing the teefer 2 driver component was.
This is the second time I have had to post this. I would appriciate it if the Moderator would not remove my comments in the future.
Naerwen.