Problems accessing domain resources.

  • Thread starter Thread starter badbadboy
  • Start date Start date
B

badbadboy

Hi folks, I'm hoping someone might be able to help me out here with a
problem that came up today at work. I have a small network,
approximately 15 users, running on W2k Server (AD enabled). All was
well with the setup until today. The problem began shortly after we
started having some issues with BusinessVision (may be the cause, may
just be the effect, I'm not sure), an accounting package we use. While
rebooting a machine to check to see if the problem with BV was fixed, I
found I no longer had access to network shares on the server, as well
as the Internet. This problem began to occur on other systems as they
were rebooted.

The desktops get an IP address from the server (I've released the
address on multiple local machines and rebooted to verify this). It
seemed to be limited to desktops running W2k, but not long before I
left today the same problem occurred on my desktop running XP Pro. I
have tried rebooting the server, thinking that would cure the issue,
but with no luck. I thought perhaps I had lost a hub, but when I tried
plugging in the ethernet cable from a computer that wasn't working into
my desktop, it worked fine (until I lost it later of course). Plugging
a working connection into a non-working computer did not however.

If I do an 'ipconfig' from a DOS prompt, I get the following (as an
example) :

IP Address. . . . . . . . . . . . : 192.168.1.65
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.5

The S.M. and D.G. settings are the same on a machine that works, and
one that doesn't (192.168.1.5 is the server address), and is what I
would always get before. I have tried pinging that default gateway
address, but get no response from a non-functioning system. I could
really use some help here, before everybody comes and lynches me :)

BB.B
 
we need more information to help. can computers ping each other? have you re-set gateway?

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Hi folks, I'm hoping someone might be able to help me out here with a
problem that came up today at work. I have a small network,
approximately 15 users, running on W2k Server (AD enabled). All was
well with the setup until today. The problem began shortly after we
started having some issues with BusinessVision (may be the cause, may
just be the effect, I'm not sure), an accounting package we use. While
rebooting a machine to check to see if the problem with BV was fixed, I
found I no longer had access to network shares on the server, as well
as the Internet. This problem began to occur on other systems as they
were rebooted.

The desktops get an IP address from the server (I've released the
address on multiple local machines and rebooted to verify this). It
seemed to be limited to desktops running W2k, but not long before I
left today the same problem occurred on my desktop running XP Pro. I
have tried rebooting the server, thinking that would cure the issue,
but with no luck. I thought perhaps I had lost a hub, but when I tried
plugging in the ethernet cable from a computer that wasn't working into
my desktop, it worked fine (until I lost it later of course). Plugging
a working connection into a non-working computer did not however.

If I do an 'ipconfig' from a DOS prompt, I get the following (as an
example) :

IP Address. . . . . . . . . . . . : 192.168.1.65
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.5

The S.M. and D.G. settings are the same on a machine that works, and
one that doesn't (192.168.1.5 is the server address), and is what I
would always get before. I have tried pinging that default gateway
address, but get no response from a non-functioning system. I could
really use some help here, before everybody comes and lynches me :)

BB.B
 
And a few more to add to Robert L's: Can you ping "localhost"? Can you ping
127.0.0.1? What is the output of "ipconfig /all" on a working and
non-working box. Do you have antivirus running on all workstations and
servers? How many switches/routers separate the various machines. Can you
ping the closest computer to you? Can you ping by IP address? Do you get an
error message when you try to ping by name? Problems like this are typical
of spyware/virus that take over DNS and attempt to act as a local proxy,
sending DNS requests to a logging server that tracks URLs you visit. If the
logging DNS server goes down, you lose all DNS name resolution. The same
thing can happen if you remove the local proxy agent without restoring the
original settings, which often happens after a spyware or virus scan. In
that case you can't even contact your local DNS server, so domain logons
(uncached) are not possible.

....kurt
we need more information to help. can computers ping each other? have you
re-set gateway?

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
Hi folks, I'm hoping someone might be able to help me out here with a
problem that came up today at work. I have a small network,
approximately 15 users, running on W2k Server (AD enabled). All was
well with the setup until today. The problem began shortly after we
started having some issues with BusinessVision (may be the cause, may
just be the effect, I'm not sure), an accounting package we use. While
rebooting a machine to check to see if the problem with BV was fixed, I
found I no longer had access to network shares on the server, as well
as the Internet. This problem began to occur on other systems as they
were rebooted.

The desktops get an IP address from the server (I've released the
address on multiple local machines and rebooted to verify this). It
seemed to be limited to desktops running W2k, but not long before I
left today the same problem occurred on my desktop running XP Pro. I
have tried rebooting the server, thinking that would cure the issue,
but with no luck. I thought perhaps I had lost a hub, but when I tried
plugging in the ethernet cable from a computer that wasn't working into
my desktop, it worked fine (until I lost it later of course). Plugging
a working connection into a non-working computer did not however.

If I do an 'ipconfig' from a DOS prompt, I get the following (as an
example) :

IP Address. . . . . . . . . . . . : 192.168.1.65
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.5

The S.M. and D.G. settings are the same on a machine that works, and
one that doesn't (192.168.1.5 is the server address), and is what I
would always get before. I have tried pinging that default gateway
address, but get no response from a non-functioning system. I could
really use some help here, before everybody comes and lynches me :)

BB.B
 
And a few more to add to Robert L's: Can you ping "localhost"? Can you ping
127.0.0.1? What is the output of "ipconfig /all" on a working and
non-working box. Do you have antivirus running on all workstations and
servers? How many switches/routers separate the various machines. Can you
ping the closest computer to you? Can you ping by IP address? Do you get an
error message when you try to ping by name?
Click to expand...

All desktops & server are running F-Prot, with latest defs. At most,
there are two hubs (not routers) between any desktop and the server
(most desktops have just one between them and the server). I thought
maybe I'd lost a hub, but a cable from a non-working machine worked
fine on a system that was having no issues at the time. I will try
pinging those this morning, as well as the ipconfig/all to see what the
results are.

Bob, you mentioned about resetting the gateway. I did reset the server
yesterday at one point (basically because I was out of ideas on what to
do next), but that didn't seem to make any difference.

I did have a similar problem to this about a year and a half ago. What
I had to do then was put the desktop on a workgroup instead of the
domain, delete the computer from AD & then re-add it, and then put the
desktop back on the domain. This seemed to fix the problem before, and
I will probably end up trying that again today as well.

BB.B
 
Back
Top