-----Original Message-----
in message
[email protected]...
: I do not think it is a connectivity issue as I am able to
: Terminal Server & PC Anywhere into that machine...
Which means it's not a connectivity issue via Terminal Server and PC
Anywhere. It's very simple. If you cannot connect to a system, it is a
connectivity issue. That does not imply it is physical which appears to be
how you are referring to it.
: trying to access the shared folders from that machine using the
: IP (not the name), the IP Is failing....
Does that imply that you can by name? Beyond services you have
authentication and "failing" is not clear. You get an error message and
usually an error number.
: is there any service, port or something that needs to be open for this
: work.
Not by default. You could have a personal firewall [ICF, ZoneAlarm, etc.],
IDS [BIPCP], infection from a worm, antivirus, or another application
blocking it. That can only be determined by investigating what is running
and which credentials are allowed.
: Please refer to my initial post for my check list.
Referring to your OP:
: I have a computer running Windows 2000 Server SP4 and I am
: unable to connect to that computer using the IP address
: for that machine.
This generally implies connectivity since most will try to connect via
\\server\share before they try \\ip\share. If you're ONLY trying \\IP, it
is incomplete.
You should get this error message:
The filename, directory name, or volume label syntax is incorrect.
: This used to work before: \\<IP address>
I doubt it since UNC requires \\server\share or \\IP\share, at a minimum but
NOT \\IP. UNC is designed to connect to a share, not a server. And if you
have multiple shares, it would not know which one to connect to if you
omitted the share.
: but now it doesn't. I haven't applied any patches or made
: any changes but all of a sudden it just doesn't work
: anymore.
....that you are aware of.
: I see "Server", and "Workstation" services running, "File
: and Printer Sharing For Microsoft Networks" is also
: checked along with "Client for Microsoft Networks". I also
: see "NetBIOS over TCP/IP" in Device Manager.
NetBIOS over TCP/IP in Device Manager? NetBIOS over TCP/IP is handled in on
the WINS tab of the advanced section of TCP/IP properties, in your network
settings of a particular network interface. However, I gave you the benefit
of the doubt and went through Device Manager looking for protocol
information which I was unable to find. NetBIOS is not a device.
: All the
: latest patches and Service Packs have already been
: installed on that machine.
Certain OEMs like Compaq, for example, require the use of THEIR own NIC
driver, not the one supplied by MSFT. It is required, should you update
your OS with SPs, then you MUST reapply your OEM drivers or you could
experience mixed results, possibly failure, especially where network
interfaces are concerned and you MUST apply them AFTER SP updates, not
before.
: Whenever I try to connect to that computer using the IP
: address, I either get "The network path was not found"
....which means the source was not able to locate the target and get a
response. That is the result error which may have one of numerous causes.
: or "No network provider accepted the given path". It used
: to work fine before and nothing has changed on that
: machine.
Logically, if nothing has changed on that machine, and if that really is the
case, then it can be eliminated and you need to look elsewhere.
: I am also able to connect to that machine using
: Terminal Server but cannot through its UNC.
Since these are services that use different ports and do not require
connection through a UNC path, they are not relative.
It appears you have checked what is supposed to be running but have you
investigated what should not be there?
Have you verified credentials at the file system and share levels?
Are you running a personal firewall?
Are you running RTAV? Is it up to date? Is it enabled?
Have you performed a:
netstat -an
....to see what is, if anything connected to your system, especially foreign
connections?
Are you running IDS? If so, is it allowing NetBIOS traffic, specifically
the ports you need connectivity to?
Please advise...
--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Online Support for IT Professionals -
http://support.microsoft.com/servicedesks/technet/default ..asp?fr=0&sd=tech
How-to: Windows 2000 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN- US;308201
FAQ W2K/2K3 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN- US;291382
.
