At least that's my guess as to what the issue might be. Sorry for
crossposting, but the protocol group doesn't get much traffic and I wanted
to try and get an answer for this ASAP.

I have one computer that can't see one of the servers on our network. It can
ping everything else, but when I try to ping
our SQL server by name or IP, I get an error "bad IP address". All other
workstations can reach this server with no problems. I'm thinking there is
some bad information stored somewhere on the workstation, but I can't figure
out what as I'm not too familiar with the network commands (i.e. arp,
nbtstat, etc). TechNet didn't help much, so hopefully somebody here has an
idea or two on what I need to do?

Thanks
Brian

Hi Brian,
Can you access other computers on your network
from this workstation by tcp/ip address? Open a dos
prompt and run ipconfig /all and verify it has a valid tcp/ip
address and the settings are correct.

"Brian" <TBone2K@themail.com> wrote in message

"Michael Giorgio - MS MVP" <Michael.Giorgio@NoSpam.mayerson.com> wrote
It does have a valid address, Michael. I can access every other computer on
the network except the SQL server.

Hi Brian,

How is the SQL server connected to the rest of the network? Is there a
router or switch separating it? What if you put a client on a hub with the
SQL server?

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.

Problem solved. I removed the network card driver and the configuration
software. I had already done that before, but maybe in a different order or
something. Anyway it works now. I still think that not being able to ping
one address is an odd symptom of a corrupt driver, but I've seen corruption
cause stranger things I guess.

Glad to hear and thank you for the update. A bad
NIC/driver would cause this type of problem. Not
being able to ping by tcp/ip address usually means
a NIC, cable, or routing problem.

"Brian" <TBone2K@themail.com> wrote in message