Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
Ever seen this one? Short of changing ports on my switch, I think I've tried everythiing else. I can join this Windows 2000 machine into my domain, map drives, see printers, etc...But I can't ping ANYTHING, even the servers that I can map too. Any ideas/suggesstions/advice?? Thanks.
You have to be using NetBios - what you are thinking of is NetBeui, there's a difference.
Do you have both protocols installed or more protocols than just Tcp/Ip? Could be that IP isnt working but you can map using NetBeui or IPX.
How about sharing some specifics. What IP and mask does your computer have? What IP and mask do some of the other servers have. This problem will not be a difficult one to fix with a bit more info.
Can you ping the loopback adapter - 127.0.0.1? Can you ping your own IP address? What message do you get when you try to ping another host?
0 
I think Glen pretty much covered everything I was about to ask except this. When you try to ping, are you trying to ping an IP address or a system name? I've seen plenty of times where one can ping an IP address and not the name of the system with that address. If there is no active directory service or WINS available on your network, you should go into your TCP/IP properties and try enabling "netbios over TCP/IP." Hope this helps some.
0
Scott,
This is not a difficoult problem to solve.
Tell me what happens when you do
to command.com and type:
IPCONFIG
try to ping the gateway
write down, and type again:
NETSTAT -A
(there is a space between netstat and -)
go to run ant type again:
WINIPCFG
tell me the what are the resoults and I tell you where the problem is.
0
Robert, I doubt you will tell him what his problem is. First, he mentions nothing about a routed network so the gateway will be irrelivant if it even exists at all.
Netstat will give very little troubleshooting info and WINIPCFG does not work on Windows 2000 so I wonder how you plan on fixing his problem.
0
You right Glen.
Somehow I focus more on TCP-IP issue and by pass his OS- my mistake-Sorry about it.
"WINPCFG" is WIN9x tool."NETSTAT" it's a very good tool to troubleshoot, shows you all established TCP connections by default.
"NETSTAT -A" will show all the ports the machine is listening to.
Is good thing to know what type of connection the computer uses ?
You can also see the packets if they send or received.
If you type "NETSTAT -P TCP -N" you will know the established current connections or
who is attached to your machine "P" stands for IP.
You might not consider these important, but I would think if don't have enough info. it's still an additionall tool to check IP connection if the one exist.
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
