After running AP, I cannot connect to my server. I reloaded Windows with SP3 and could map shares properly. Then I ran AP in what should be a pretty simple fashion. Afterwards, I can't get to the server again. The AP I used in the second test was downloaded today (1/20/2010).
Any tips will be most appreciated.
Cannot Connect To Server
Started by Coast Ranger, Jan 20 2010 06:13 PM
4 replies to this topic
#1
Posted 20 January 2010 - 06:13 PM
#2
Posted 20 January 2010 - 09:09 PM
well, when this issue happened, you tried the most common mistake (aka install everything at once, even the tweaks)? certain tweaks enforce network security by forcing the usage of an user password to log into an server or even to another station that is acting as an server. bypass that is pretty simple: do not leave an blank password into the user account and be sure than in the machine that is acting as an server you have an user account with an password.
if you tried the tweaks, when running autopatcher you will see the tweak tagged as installed. if is this the case, just right-click the tweak and select "uninstall"
for more, please state your selections
[]s
if you tried the tweaks, when running autopatcher you will see the tweak tagged as installed. if is this the case, just right-click the tweak and select "uninstall"
for more, please state your selections
[]s
#3
Posted 21 January 2010 - 04:32 PM
Thanks for the reply Cristiano.
Yes, I do everything in one step. I take all the Critical, none of the Recommended, some of the Updated and many of the Tweaks. Note the attached images for details.
When I connect to the server, my generic Windows user doesn't have a password. To connect, I have to "Connect using a different name" and supply a password. Usually it just asks for a name and password to connect to the shared folder. The catch is that any name and password supplied will not allow access. If I create a user with a good name and password, it will not access. I might understand what you said to mean that if the first user does not have a password, then it will never have access even with a good name and password. If that is the case, I'm not familiar with that bug/tweak. If I can identify it, I can undo it and life will be good again.
I attached some screen shots that show what tweaks I selected. If someone can spot which one is causing my problem, I would be most appreciative.
BTW, this is a really nice board. Can I ask who did it?
Thanks,
CR
Yes, I do everything in one step. I take all the Critical, none of the Recommended, some of the Updated and many of the Tweaks. Note the attached images for details.
When I connect to the server, my generic Windows user doesn't have a password. To connect, I have to "Connect using a different name" and supply a password. Usually it just asks for a name and password to connect to the shared folder. The catch is that any name and password supplied will not allow access. If I create a user with a good name and password, it will not access. I might understand what you said to mean that if the first user does not have a password, then it will never have access even with a good name and password. If that is the case, I'm not familiar with that bug/tweak. If I can identify it, I can undo it and life will be good again.
I attached some screen shots that show what tweaks I selected. If someone can spot which one is causing my problem, I would be most appreciative.
BTW, this is a really nice board. Can I ask who did it?
Thanks,
CR
Attached Files
#4
Posted 21 January 2010 - 09:35 PM
well, this issue is related to those tweaks (security):
remove ipc$
disable default hidden administrative shares
just right click, uninstall and then reboot. your issue shall be solved after that
> Can I ask who did it?
yep. this boards runs IPB3 with some changes done by Frank (the owner of our host and our very boss) and Caesar. but i don't remember the names of everyone involved in this
[]s
remove ipc$
disable default hidden administrative shares
just right click, uninstall and then reboot. your issue shall be solved after that
> Can I ask who did it?
yep. this boards runs IPB3 with some changes done by Frank (the owner of our host and our very boss) and Caesar. but i don't remember the names of everyone involved in this
[]s
Edited by Cristiano, 21 January 2010 - 09:36 PM.
#5
Posted 21 April 2010 - 05:20 PM
After messing with a couple of ideas, I stumbled on one that worked.
In regedit go to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
Change DWORD entry lmcompatibilitylevel from 3 to 1
Restart
It worked for me, maybe it will for you.
CR
In regedit go to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
Change DWORD entry lmcompatibilitylevel from 3 to 1
Restart
It worked for me, maybe it will for you.
CR
Edited by Coast Ranger, 21 April 2010 - 05:21 PM.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users












