That is the symptom you will get if the server has nbt disabled on the internet NIC. This is a good thing in that as I mentioned, you can't even attempt to login. Opening up access to drive letters and whatnot are just some things that nimda will do. But it will not enable NBT on a disabled machine. So This machine was more than likely infected by one of the IIS exploits but yet NBT is still secure.
At 10/12/2001 10:37 PM, you wrote: >OK, is NBT access possible going from an @home machine? I keep getting an >error box that "windows cannot find \\ipaddyhere\c$" I know the nimda >infected machine is there because I can ping it...no it hasnt been patched >because the nimda request just came in. > >At 10:29 PM 10/12/2001 -0500, you wrote: >>For general information.. You did use NBT... NetBios Transport.. >>This is how you obtained IPC$ access to the box. \\ipaddress or >>\\computer name >>uses Netbios. the command mentioned earlier (nbtstat) lets you gather a >>little info. > > > > >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >Chris Kafer http://www.grad-college.iastate.edu/ippm/ippmhomepage.html >ICQ: 12594489 >PGP key available http://thornlab2.bb.iastate.edu > > >-------------------------------------------------------------------------------- >For unsubscription of this list send an email to [EMAIL PROTECTED] with >email >data containing unsubscribe emailadd sambar -------------------------------------------------------------------------------- For unsubscription of this list send an email to [EMAIL PROTECTED] with email data containing unsubscribe emailadd sambar
