Can not conect to server shares or join domain

  • Thread starter Thread starter Dan V
  • Start date Start date
D

Dan V

i tried all that and samething, Heres what fixed it.
I unistalled Spybot SD and Virtual Box. I dont understand why all of a
sudden those apps were the issue. I dont think it was spybot i think it was
Virtual Box. Weird. This was working fine for a long time then all of a
sudden it stopped. Oh Well it works now.


I have a windows xp pro sp3 with all the updates and virus scanner on it
with
no viruses. I have a win2003 server setup in a domain. my xp computer was
connected to the domain fine and i was accessing shares fine ever since i
setup the server and client. Yesterday the client was running slow and
acting
like wierd so i rebooted it cause normally i leave my pc on all the time.
When i booted back into windows i couldn't connect to my mapped drives. I
rebooted the server and the same thing i keep getting error Network Path
not
found. I can ping by name and ip. So then i removed the pc from the domain
and tried to rejoin the to the domain and now i cant rejoin to the domain.
I
even tried to change the computer name and same thing. this is the error i
get when i try to join to the domain. " The following error occurred
attempting to join the domain "domain.local" The format of the specified
network name in invalid. I ran chkdisk /r and ran rootkit scanners and 3
different virus scanners and no viruses are found. I also ran scf /
scannow
and still same issue. Any suggest will be grateful.

thanks
Click to expand...

Sounds like your "enhanced" security software (anti-virus and / or
firewall) is set to block your network access. To confirm this, try
to access the "shares" via the IP address instead.
 
I have a windows xp pro sp3 with all the updates and virus scanner on it with
no viruses. I have a win2003 server setup in a domain. my xp computer was
connected to the domain fine and i was accessing shares fine ever since i
setup the server and client. Yesterday the client was running slow and acting
like wierd so i rebooted it cause normally i leave my pc on all the time.
When i booted back into windows i couldn't connect to my mapped drives. I
rebooted the server and the same thing i keep getting error Network Path not
found. I can ping by name and ip. So then i removed the pc from the domain
and tried to rejoin the to the domain and now i cant rejoin to the domain. I
even tried to change the computer name and same thing. this is the error i
get when i try to join to the domain. " The following error occurred
attempting to join the domain "domain.local" The format of the specified
network name in invalid. I ran chkdisk /r and ran rootkit scanners and 3
different virus scanners and no viruses are found. I also ran scf / scannow
and still same issue. Any suggest will be grateful.

thanks
 
I have a windows xp pro sp3 with all the updates and virus scanner on it with
no viruses. I have a win2003 server setup in a domain. my xp computer was
connected to the domain fine and i was accessing shares fine ever since i
setup the server and client. Yesterday the client was running slow and acting
like wierd so i rebooted it cause normally i leave my pc on all the time.
When i booted back into windows i couldn't connect to my mapped drives. I
rebooted the server and the same thing i keep getting error Network Path not
found. I can ping by name and ip. So then i removed the pc from the domain
and tried to rejoin the to the domain and now i cant rejoin to the domain.. I
even tried to change the computer name and same thing. this is the error i
get when i try to join to the domain. " The following error occurred
attempting to join the domain "domain.local" The format of the specified
network name in invalid. I ran chkdisk /r and ran rootkit scanners and 3
different virus scanners and no viruses are found. I also ran scf / scannow
and still same issue. Any suggest will be grateful.

thanks
Click to expand...

Sounds like your "enhanced" security software (anti-virus and / or
firewall) is set to block your network access. To confirm this, try
to access the "shares" via the IP address instead.
 
Back
Top