After working with Windows Server since NT 3.51, this was kind of a first for me. Here's the scenario.
After no issues accessing a Windows Server 2012 R2 network share for 2 years, a Win 7 Pro workstation all of a sudden can access the mapped drive to the share, but cannot see all subfolders underneath it. Only one is visible, not the other 20 or so.
When I log out as the user and login as the domain admin account, the issue persists on the workstation. Just this one workstation.
Nothing has changed in terms of the share or NTFS permissions on the server-side of things.
I look in the server event logs as well as the workstation's and don't see anything striking.
I removed the workstation from the domain and add it again. The issue still persists.
The workaround is that I created a second share to the same resource on the server-side of things. Mapping a different drive letter to this new share, the workstation can see everything again.
My only guess would be some sort of old school SAM database corruption or something? I recall years ago I had a Windows 2000 Server that would lose Computer Browser functionality due to some odd SAM database corruption. The only solution back then was to reboot the server. It was the PDC and couldn't even browse its own network shares.
Related
I have several windows shares hosted on a PC running Win7x64. This machine is also hosting a basic website via IIS7. Whenever I deploy a new copy of the website to IIS any WinXP users connected to the shares on that machine get disconected.
After some period of time (20mins or so) the shares all start working again.
This only seems to affect WinXP clients, with them recieving this error message described here: http://support.microsoft.com/kb/890413.
The resolution provided by Microsoft works, but it means that everything I deploy a new copy of the website all of my users have to go through this hassle.
Any IIS experts out there know what is happening, or how to resolve this?
Thanks
The LAN which has about a half dozen windows xp professional pcs and one windows 7 professional pc.
A jet/access '97 database file is acting as the database.
The method of acccess is via dao (DAO350.dll) and the front end app is written in vb6.
When an instance is created it immediately opens a global database object which it keeps open for the duration of its lifetime.
The windows 7 machine was acting as the fileserver for the last few months without any glitches.
Within the last week what's happened is that instances of the app will work for a while (say 30 mins) on the xp machines and then will fail on database operations, reporting connection errors (eg disk or network error or unable to find such and such a table.
Instances on the windows 7 machine work normally.
Moving the database file to one of the xp machines has the effect that the app works fine on ALL the xp machines but the error occurs on the windows 7 machine instead.
Just before the problem became apparent a newer version of the app was installed.
Uninstalling and installing the previous version did not solve the problem.
No other network changes that I know of were made although I am not entirely sure about this as the hardware guy did apparently visit about the same time the problems arose, perhaps even to do something concerning online backing up of data. (There is data storage on more than one computer) Apparently he did not go near the win 7 machine.
Finally I know not very much about networks so please forgive me if the information I provide here is superfluous or deficient.
I have tried turning off antivirus on the win 7 machine, restarting etc but nothing seems to work.
It is planned to move our database from jet to sql server express in the future.
I need some suggestions as to the possible causes of this so that I can investigate it further. Any suggestions would be gretly appreciated
UPDATE 08/02/2011
The issue has been resolved by the hardware guy who visited the client today. The problem was that on this particular LAN the IP addresses were allocated dynamically except for the Win 7 machine which had a static IP address.
The static address happened to lie within the range from which the dynamic addresses were being selected. This wasn't a problem until last week when a dynamic address was generated that matched the static one and gave rise to the problems I described above.
Thanks to everyone for their input and thanks for not closing the question.
Having smart knowledgeable people to call on is a great help when you're under pressure from an unhappy customer and the gaps in your own knowledge mean that you can't confidently state that your software is definitely not to blame.
I'd try:
Validate that same DAO and ODBC-drivers is used on both xp- and vista machines.
Is LAN single broadcast domain? If not, rewire. (If routers required make
sure WINS is working)
Upgrade to ms-sql. It could be just a day of well worth work, ;-)
regards,
//t
I have a very strange problem with Visual Source Safe. I use VSS as a add-on with VS 2008 in a corporate intranet with 5 other colleagues. My VS stops working after 5 p.m. most of days with complaining can not connect Source Safe. I'm running VS 2008 and VSS 2005 on Vista and no other one in corporate have such a problem.
What do you think about its cause?
Is there any log for VSS?
You probably have logon restrictions on your domain account.
VSS is a file based source control system and it works via access to a net work share. Account logon restrictions would prevent you from gaining access to the share at certain times.
To test this theory try this:
Get the share that VSS lives in. It should be in the form \\SERVER\SHARE.
Open a command prompt
Type NET USE this will show you all your connections
If connected to the share type NET USE Z: /delete (with Z: being the assigned drive letter for that share)
Type NET USE * \\SERVER\SHARE
If this theory is correct, before 5 your will get command completed sucessfully, but after 5 you will get access denied
A couple of questions
Has it ever worked past 5pm? If it has is there an event you can correlate to when it stopped working?
Can you access VSS through VSS Explorer when you can't access it through VS.NET
Is the VSS database on a remote server or shared drive? If so can you access that drive after 5pm? VSS is just a bunch of files on the disk. Can you see those files outside of VSS or VS.NET?
Any chance someone is doing a backup or something similar to the VSS machine that is bringing the box down? Can you ping the VSS server after 5pm?
I'm using windows XP to do the development.
Since I working remotely from home, I found a serous problem, some applications for instance MS excel, even just open up the start menu became to extremely slow .
If I logged into the local pc without domain then the problem fixed, my domain user account has 300 mb local user profile.
Anybody know how to fix this?
Thanks
The problem is caused by My documents, as it is been referred to the domain server which is unavailable.
At work, I running Vista Business on a lavishly new PC, which runs great excepting two issues. In order of annoyance, but not importance:
When I reboot the machine, the Windows Splash is presented asking me to Press Ctrl + ALT + DELETE so I can logon. It takes three to five minutes and seceral key presses for me to be prompted to select my user account. After which, everything works like a charm.
As part of my duties with the firm, I am responsible for emergency work on a rotating basis and deploying patches during off-business hours. I have been given an older laptop with XPSP2 (downloading 3 for kicks right now) which I use for browsing with the intention of RDP to my desktop in the offices. If I am connected at the domain through conventional means, I am able to RDP. However, if I am using an existing broadbad connection with VPN, I am not able to get access. I am able to access other servers, desktops running a variety of OS'es including Vista.
So umm any ideas guys?
as for 2 - this happens with some proprietary VPN software (i.e. Cisco). My solution was to perform my work duties in a Virtual PC (which doesn't need its normal LAN abilities) and do my other network/internet tasks in the physical machine.
I have a Vista at work and uses my home PC to rdc in for support work. I do not experience your problem 1 so I cannot offer any advice. For your second problem have you tried the IP address instead of the machine name? We have situations where sometimes the dns resolution in the office network is not accurate.
Do you have remote access enabled, either on the machine, via group policy?
If not, you might have to go into the Control Panel\System and Maintenance\System and choose Remote Settings (from the menu on the left).
That will show you the options for Remote Deskop, including Don't allow connections, Allow connections from any version of Remote Desktop, and Allow connections from computers running Remote Desktop with Network Level Authentication (which might be the hang up you are experiencing over the VPN).
Good Luck.
I have to chalk this up to "something wierd with my laptop" as I was able to download RoyalTS and connect to the machine just fine. I had Remote connections permitted, firewall disabled, McAffee gone and others could access the machine.
The advice garnered above is excellent and useful for your typical rdp connections