D
dj
you can do some more testing
setup telnet server on port 135 and 139 if it connects.
setup telnet server on port 135 and 139 if it connects.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
P
Paul Klose
I could not connect to either port using Telnet.
C
Chris
I could not connect to either port using Telnet.
I am having a very similar issue. I have a server in a collocation
facility that is behind a firewall, but my IP (static) has access to
the server through the firewall.
I had no problems getting to the server (it is a Windows 2000 Server)
with a UNC path, like \\MachineName\MyShare$ before yesterday. Now I
can't get to the machine with the UNC path at all. I can use Terminal
Services to remote control the machine, I can get to the web
application on port 80 with no problems. When I try to get to the
machine with the UNC path I get "the network path was not found". It
pings fine etc. I have scanned both machine for a virus, none were
found.
I did just install the security patch for the Blaster worm, the day
before I noticed that I could not connect. Does anyone one know if
that would have changes a setting or something else to cause this? I
have not made any configuration changes at all other than the patch.
Any help would be GREAT!
Thank you in advance
P
Paul Klose
This appears to be the identical problem that I am having. My server
is also in a co-location facility, but there is no firewall that I am
aware of and also according to my hosting company.
In my case, I installed the Windows security patch 823980 that
prevents the Blaster virus on 8/1, but the problem didn't appear until
8/14 ... so I don't think they are connected.
If my machine has the IP address xxx.yyy.zzz.111, is it possible for
another customer at the co-location facility (e.g. xxx.yyy.zzz.222) to
be able to firewall my system? If so, is there a way to detect the
existence of such a firewall?
is also in a co-location facility, but there is no firewall that I am
aware of and also according to my hosting company.
In my case, I installed the Windows security patch 823980 that
prevents the Blaster virus on 8/1, but the problem didn't appear until
8/14 ... so I don't think they are connected.
If my machine has the IP address xxx.yyy.zzz.111, is it possible for
another customer at the co-location facility (e.g. xxx.yyy.zzz.222) to
be able to firewall my system? If so, is there a way to detect the
existence of such a firewall?
C
Chris
Does anyone have a fix for this issues?
This appears to be the identical problem that I am having. My server
is also in a co-location facility, but there is no firewall that I am
aware of and also according to my hosting company.
In my case, I installed the Windows security patch 823980 that
prevents the Blaster virus on 8/1, but the problem didn't appear until
8/14 ... so I don't think they are connected.
If my machine has the IP address xxx.yyy.zzz.111, is it possible for
another customer at the co-location facility (e.g. xxx.yyy.zzz.222) to
be able to firewall my system? If so, is there a way to detect the
existence of such a firewall?