Hello, With one of the server in our domain, we are facing issue with windows logon. Every time it is taking very long to logon. When I checked the Event Viewer I got following info. The important observation is that if we access the machine via machine name then windows logon goes normally. Similarly when I try to access the machine via \\192.168.15.1\sharedfolder then its again taking very long, where as with \\servername\sharedfolder, it is not taking long. Event info. from event viewer: --------------------------------------- The winlogon notification subscriber <GPClient> took 255 second(s) to handle the notification event (Logon). Log Name: Application Source: Microsoft-Windows-Winlogon Date: 10/6/2009 7:22:20 AM Event ID: 6006 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: virtualsrv1 Description: The winlogon notification subscriber <GPClient> took 255 second(s) to handle the notification event (Logon). Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Winlogon" Guid="{DBE9B383-7CF3-4331-91CC-A3CB16A3B538}" EventSourceName="Wlclntfy" /> <EventID Qualifiers="32768">6006</EventID> <Version>0</Version> <Level>3</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2009-10-06T05:22:20.000Z" /> <EventRecordID>4509</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>virtualsrv113.MEDINET.priv</Computer> <Security /> </System> <EventData> <Data>GPClient</Data> <Data>255</Data> <Data>Logon</Data> <Binary>61C08F00</Binary> </EventData> </Event> Thanks Sandip

Hello,logon means for my point of view weither using Remote desktop or sitting in front of the server.Or did i misunderstand you then, check if following GPO settings is enabled and slows down the logon, disable it for a test:User Configuration\ Administrative Templates\ System\ Scripts "Run logon scripts synchronously"You case sounds that you mean network mappings created to a shared folder have connection problems with ip address. So make also sure that users have the correct permissions for mapped drives that are added with logon scripts.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.

Hello, 1) With Remote Desktop login via ip address (for e.g. 192.168.15.1 \ or with live ip) talking long In local network if I access via remote desktop but with servername then we don't face any problem with network access. 2) With network access via ip address (for e.g. \\192.168.15.1\Shared folder) (where as if I access with machine name e.g. \\servername\sharedfolder we don't face any problem with network access) Thanks Sandip

Hello,please post an unedited ipconfig /all from the server and a normal running server and your DC/DNS server to exclude DNS as a problem.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Sandip, So when you access using IPaddress\shared folder from the destination , its taking long time to open the shares but this doesnt happen when you are using Netbios name. can you please perform the same task locally on to the server \\ipaddress\sharename , and check if the issue occuring locally as well.Did you check the issue with multiple clients ? or only accessing the server share from one client ?, this is bit strange i have seen issue accessing via netbios / FQDN takes long time but not with IP as it doesnt require any name resolution components ( dll's / sys files ) to get included. can you please tell us the server version and the SP levels along with the meinolf suggestion. sainath !analyze

Hi Sandip, Did you had a chance to go through our suggestions , if you need further assistance pelase do post back in the forums.sainath !analyze

Hi,I found the cause of problem.Cause: The Alternate DNS was set wrong.In my case I'd same Alternate DNS specified as the Default gateway.I've corrected this setting and problem gone!Thanks for the support.Sandip