Windows 8 PC Slow Connection to Domain Network

I have a Windows 8 laptop connected to a domain. It is connected Via Ethernet Cable and the connection is extremely slow in sync center and accessing network drives... Basically, doing anything on the network. I am not sure why it is going slow. There are
hundreds of computers/laptops connected to the domain network and no one else is experiencing this issue.
Any ideas/suggestions?
Don't forget to mark the post that solved your issue as "Answered." By marking the Answer you are enabling users with similar issues to find what helped you. Lewis Renwick - IT Professional

Hi,
I want to know the size of the offline file, because Windows syncs your offline files for you automatically when a network file is changed, the offline copy stored on your computer is also updated, and vice versa. So, if the file size is too large
it will cause the slow performance. Meanwhile, I suggest to trace the network performance with Netmonitor, this helps to analyze the network performance problem, you can download it here, after downloading and installing it, you can “new capture tab” and then
click “start” to create a new trace file. This will give which protocol is using large resources,
http://www.microsoft.com/en-hk/download/details.aspx?id=4865
Besides, check whether you have any other anti-virus software that is scanning files or documents on your computer, that will also cause a slow performance.
Regards
Wade Liu
TechNet Community Support

Similar Messages

Windows PCs extremely slow in Airport extreme networks

We have a large deployment of Aiport extreme mesh network. Since the beginning we been experiencing issues with all PCs. Usually my macbook pro will do a speedtest and give 30-35mb/s on it while the PCs will only do 2-3 and its intermitent. They are always reporting connectivity drops too. Also access to a NAS is extemely slow from the PCs. Anyone have any clue as to how to fix this. I assume its a windows issue but after doing lots or research everyone reports it but no one has been able to fix it. Any clues as to what could be the culprit. All PCs are 2011 or late 2010 Lenovo with windows 7
Thanks for any help
t

Thanks. If the problem occurs on every Mac or other device using that base station, there really is not anything else worth checking. It could be a DNS problem associated with your ISP, or it could be a corrupted parameter in the base station. To fix the latter would require a "hard reset" followed by configuring it again:
To "hard reset" an AirPort Base Station: make sure it's powered up, then press and hold its tiny reset button and keep it depressed for five to ten seconds, long enough for its LED to flash amber rapidly. Release the reset button. Then, the LED will glow amber steadily for about a minute. Then, it will flash amber, slowly, about once every second or two, waiting for you to configure it with AirPort Utility.
If the slow page loads still occur, you might temporarily try a public DNS such as OpenDNS, which will bypass the DNS your ISP uses. You can try that before or after resetting the base station.

Macbook , Windows & external hard drive connection on Wifi Network

I am intrested in connecting 2 Macbooks & 2 Windows operating Netbooks & a 1TB external hard drive on a wireless network operating at my apartment .The purpose of connecting the netbooks is purely personal for sharing of music & movies via network .
The modem , we have is the one supplied by telecom company ( STC , Saudi Arabia ) , nothing sophisticated about that .
Can you guys advise , what will be needed to connect the above mentioned stuff ?
Will a need a new modem ? If yes , which is the best ? Will ethernet gigabyte switch be also required ?
Also any suggestions for the external hard drive ?
Is the connectivity possible with Mac OS & WIndows .
Looking forward to your suggestions & solutions

Yes! it's that easy! The hard drive in the TC will be available to anyone who is on the administrative account. By default the TC and AExtreme will send two signals, one, for you and sharing your important information and a second one for guests that you may not want seeing all your files. It's quite simple.
And since there is a USB port on the back of both of these Routers, then you wil be able to also plug a usb hub with however many hard drive you want.
So if you have a hard drive that is big enough for your needs already, you could be fine getting the Airport Extreme. But again, I wanted both so I got the TCapsule.
Please note, you're looking for a router. The modem is usually provided by your ISP, however I bought one because I would have ended up buying it in the end with the rental system put in place for it. And I wouldn't get to keep the modem after I was done with the ISP (internet service provider).
So you are in the market for a ROUTER just to be clear, the modem is what recieves the signal from the ISP the router is what you can use to broadcast it and connect multiple devices to. Make sure all of your ethernet cables say CAT 6 on them, this is the gigabit connector, the other ones aren't so fast. Niether devices come with Ethernet Cables! this was a big pieve of mine but other then that I am super happy with my Time Capsule and given what you said you wanted to do, I think you will be too!!
to round it all up, I have a Time Capsule that I also have a usb storage device plugged into via a usb hub broadcasting these hdd's to anything that you want and nothing that you don't (admin user, guest user) but still allowing everyone to have high speed internet.
Security measures you should take with your router is setting up a WPA2 pass key and also to not broadcast your signal. Meaning you'll have to manually type it into whatever device you're connecting with. with all of this, your information will be wireless and secure.
hope this helps! I'm excited for you! let us know what you end up doing.

Win7 Pro ws, connected to Active domain network SBS2K8 server, but firewall Public networks - Connected.

Win7 Pro workstation shows active domain network but firewall thinks it's connected to Public Network.
Other Win7 Pro workstations in the same domain have no problems and show the correct Domain Network: Connected in the firewall panel.
SBS2K8 server can't see security status of, or offer remote assistance to this ws until it's firewall is disabled.
Domain name is correct. Machine IS logged into the domain. User has normal rights / Admin account. Just like everyone else.
This system has current AV, but disabling it (not uninstalling) makes no difference. All the machine have the same AV.
Not a wireless network, standard CAT5. Network connectivity appears normal: Access files on server share, browse internet, etc... all just fine.
Already installed:
http://support.microsoft.com/kb/2524478
I've seen
http://social.technet.microsoft.com/Forums/en-US/7bce7005-b820-4340-a4c8-68025272d3aa/windows-firewall-falsely-shows-connected-to-public-network-when-my-computer-is-joined-to-domain?forum=w7itprosecurity
But this is not a virtual machine. It does run the WinXP mode V but this is happening in the regular Win7 OS.

Went back to the machine today to check your suggestions, and... now it's correct!
Hi,
How many network adapter card do you have of your computer?
Just the one. A Realtek PCIe GBE
Check whether the DNS is the correct one you had deployed
Yes, DNS is set to the 2k8 server IP as primary, and the secondary is OpenDNS.
and update the group policy by using this command ”gpupdate /force”.
Done, didn't appear to log any changes.
Check the registry key at “HKEY_Local_Machine\Software\Microsoft\Windows\CurrentVersion\Group Policy\History\NetworkName”
The NetworkName should be the domain name, when you get this done you will get a domain network profile, then restart your computer.
This key does exist and is the correct domain name.
More information refer to this article:
http://blogs.technet.com/b/networking/archive/2010/09/08/network-location-awareness-nla-and-how-it-relates-to-windows-firewall-profiles.aspx
I think this is the answer you want.
Thanks for that. I've read through it and will keep it on file if the problem returns.
Regards
v-yamliu

Snow Leopard Server's slow connection when connected to AirPort Exteme

Hi,
I've been experiencing slow connections ever since I hooked up my Mac Pro server directly(via ethernet) to my AirPort Extreme. Previously, the Mac Pro is connected to a switch, the AE is connected to this switch as well. Everything's fine until we decided to connect the Mac Pro server to the AE directly. Now we are having slow connection and checking Network Utility, it shows that en0 is receiving errors when previously there is none. I have connected a client computer on the same cable and it receives no errors. It's just the server that's receiving these errors. To clarify thing up my server's network configuration is as follows:
IP address: 10.0.1.201
Subnet: 255.255.255.0
Router: 10.0.1.1
DNS: 10.0.1.201
Search domain: example.net
I have configured my DNS server to use 10.0.1.1(AE's IP) as the Forwarder IP address so that my server and other client computers can still connect to the internet.
Checking the client computers connected on the same network, they are experiencing slow connections to the server as well.
There must be something that I need to set on this thing to make things work, any help would be much appreciated.
Thanks and regards,
Andrew

I forgot to check my cables. Apparently they have used crossed-cable for the previous Mac Pro to switch connection. After connecting the server to our AirPort Extreme things got a little sticky, using a straight cable did the trick.

IPod Touch cannot connect to wireless network

I have a 1 TB, dual-band time capsule with a wireless network created to share our broadband internet connection for our main computer (the iMac), a windows PC, an iPhone 3G, and a 2nd gen iPod touch to connect to the internet. Wireless security for this network is WPA/WPA2 Personal. The windows box and the iPhone 3G connect without problem, but the iPod touch does not seem to connect correctly. The device sees the network, prompts for the password, and seems to be connected (wi-fi symbol visible in top left corner of device), but when trying to view a website using the Safari app, the screen dims and an endless "Connecting..." message is visible. Furthermore, when trying to update e-mail, I get a message that the connection to the server failed.
It is worth noting that the iPod did not always have this problem. It was able to connect to the wi-fi network until a few weeks ago. This may have been due to the upgrade to Snow Leopard, or perhaps due to an incident where the windows PC lost its connection to the network. When this occurred, I had to disable all security on the network, connect the PC to the network, then re-enable security (as I had to do when first installing the Time Capsule; for whatever reason, the windows box had a hard time joining the network with security enabled). Anyway, one of these two events is the likely cause of the iPod suddenly being unable to connect; I'm sorry to say that I'm uncertain as to which one, because my wife uses the device sporadically, so we cannot pinpoint exactly when this difficulty started.
As for attempted solutions, I tried resetting the iPod back to factory settings, only to have the same connection issues. I also changed the network security settings to None, and attempted to connect the iPod to the network (even though it should have no problem connecting to a secure network), but still no go. I am short on ideas for a fix, and would gladly welcome any advice the community has to offer. Thank you in advance for your assistance.

Pretty much the same thing happened to me. My new Touch connects fine to my work wireless network (WEP64) - still does. But my home wireless network is SOL. I can join the router, wireless icon is in upper left corner (although gray, not green). I can even see the Touch from my router (Verizon FIOS). All other laptops in the house including wireless TiVo work flawlessly. I have not undone my security on my router yet - looks like it won't help. I have tried using static IP and I can still see iPod from router. But I cannot browse, go to AppStore, check email (which works great from work network), and have exact same error messages as above post. It has to be a security thing somewhere, I just didn't want to mess with router if I didn't have to. If I figure it out, I will post here........

Windows Domain Controller on Windows Server 2012 R2: Hyper-V roaming profiles not loading due to slow connection

I have racked my brain and done everything that I know to do for about two weeks now. I am setting up a new system at our fire department and I am having the worst luck with getting the workstations to login to the domain controller with roaming
profiles. It keeps telling me that the roaming profile could not be loaded because of a slow connection. These are workstations that are connected directly to the switch that the DC is connected to. I have tried multiple connections regarding
the layout (DC into the router, router into the switch). The router is a Cisco RV220W. I have two VLANS, one for public and one for private domain. The Private VLAN has DHCP turned off since I am providing it through the DC. I currently
have a connection from the Private VLAN going to the unmanaged switch that the workstations and server are plugged into.
The server is a Dell PowerEdge R420 that has 6 NIC ports (1 dual port and 1 quad port). I have a virtual switch setup on Hyper-V for an external port (let's say Card 2 Port 3) that is assigned to the WS 2012R2 Domain Controller. The DC can see
the internet fine and the workstations can connect to the shared folders on the server. I can retrieve files by just using the computer name or FQDN. The DC is also running DNS and DHCP. The DNS has the _msdcs setup from when I installed
the active directory role. I have attempted to assign static IP addresses to the workstations:
IP:                     10.0.0.80
Subnet:             255.255.255.0
IPV4 Gateway: 10.0.0.1
IPV4 DNS:        10.0.0.12
I've attempted "append the specific DNS suffix", I've "registered the connection in DNS", I've used "use this connections suffix in DNS registration".
The server is assigned:
IP:                     10.0.0.12
Subnet:             255.255.255.0
IPV4 Gateway: 10.0.0.1
IPV4 DNS:         10.0.0.12
The DNS entries have forwarders that forward to my ISP DNS servers for lookup
I've enabled and disabled DHCP, I've installed a new VM just to create another DC to make sure that I didn't goof up when I created it.
I've lost my patience with this project and am sinking fast. Can someone please offer some advice as to what I've done wrong? I've created this exact scenario at work many times but, I've never done it with Windows Server 2012. Is this
possibly something to do with the Dell PowerEdge server (Generation 12) with the SR-IOV? I am going to attempt to work on it some more tomorrow when I get over there. I think there may be an issue with the SR-IOV not being enabled on the machine
through the Dell Bios. Would the SR-IOV really cause the workstations to report a slow connection? When I login at the domain controller the roaming profiles and folder redirection work fine so, I know the GPO settings are correct. I don't
have "ignore slow connections" or any of those GPO's set. I need to get it working the correct way so, I didn't want to fool the server when there is another underlying problem. Any help that someone can offer, I am more than willing
to listen. If you need more information, please ask.
Thanks,
Jay

So, I've managed to research this some more since Thursday and I've come to the conclusion that Hyper-V does a horrible job of supporting Qualcomm NIC cards. That's the only thing I can conclude as far as where the issue is originating. I've read many
post and walkthroughs but nothing that has helped. The issue wasn't with any settings in the domain controller. The issue was that there really is a slow connection originating at the domain controller that is a VM and has network connectivity through the
virtual switch from Hyper-V. So, next question is, how do I get the DC to have better connectivity through the NIC that Hyper-V won't give it? If hyper-v would allow passthrough, this would be so much simpler. VM-ware is looking really good at this point.
Im disappointed in MS right now.

Domained laptop - slow logon when connected to non-domain network

Hi,
I'm looking for ideas on how to solve or workaround this issue, so any help would be appreciated. Please note that this doesn't appear to be the usual type of "slow login" problem - in fact I'm pretty certain the issue is caused by public DNS
servers which return placeholder IP addresses for unknown domains, rather than correctly reporting them as being unknown, which is making XP "hang up" looking for servers which don't really exist. Either way, it's causing a lot of problems for our remote
users.
The scenario is this. When domain-member laptops are not on the domain network, they can take anywhere between 5-30 minutes to login. This issue only occurs when the network they're connected to presents DNS servers which resolve unknown DNS
hosts/domains to "placeholder" sites. Whilst Windows 7 laptops do also seem to suffer from this, login delays on those are at worst a couple of minutes, whereas the Windows XP machines are affected for much longer.
Maybe a bit more info will make it clearer :)
The AD namespace shares the external domain, and there are public DNS records for the external domain, but obviously not for internal hosts (like DCs). So internally, the FQDNs of the domain controllers are "DC1.company.com", "DC2.company.com" etc.
When the laptop is connected to users home network, users can logon quickly (<30 seconds), as long as the DNS server offered by DHCP on that network doesn't return an IP for hosts/domains which don't exist publicly. If they do, login takes 5-30 minutes.
I've confirmed this by doing a lookup of the domain on the affected networks to ascertain which DNS servers return placeholder IPs rather than reporting that name resolution isn't possible. For example, OpenDNS's servers (208.67.222.222, 208.67.220.220)
return placeholders, Google's (8.8.8.8, 8.8.4.4) don't. Using OpenDNS to lookup "dc1.company.com" returns their placeholder IP of 67.215.65.132, using Google's returns "can't find dc1.company.com: Non-existent domain". OpenDNS is being used
as an example, increasingly ISP's seem to be using redirection, we're getting this issue with BT and Virgin Media networks, plus a couple of others.
So, if I manually set DNS on a laptop to use Google's servers, then connect it to one of the affected networks, login is virtually instantaneous. I remove the manually configured DNS servers and allow DHCP to present the ISP's own servers, login is
seriously delayed.
From this I can only assume that the fact that the names are resolving at all is causing the delay. I've removed possibly contributory factors from the equation, such as roaming profiles, redirected folders, mapped drives, group policy etc which the
workstation might be trying to access and causing a delay, as well as checking that fast logon optimization is active.
At the moment we're having to tell users to not connect to the network until after they've logged in, which you'd think wouldn't be that big a deal but you know what users are like :)
I appreciate this issue really seems due to bad practice by ISPs rather than with Windows itself, but we really need a fix we can apply ourselves. Reconfiguring users' home networks really isn't an option, there's too many of them, plus that wouldn't
solve the problem when they're using other networks (hotels etc). I don't think setting "good" DNS servers manually is an option, certainly I can't think of a way that would still work when they're connected to our internal LAN.
I'm thinking there must be some way we can set a timeout or something on the workstations so they don't spend so long trying to communicate with what they think are domain servers, but dispite much searching, I've been unable to find anything that works.
So, any help would be gratefully recieved.
Thanks

Thanks for the reply Martin, unfortunately it didn't help matters, but after pondering for a while (and eventually kicking myself for missing something so obvious) I did come up with a solution.
Basically, just set up public DNS A records for the internal servers and point them to 127.0.0.1 (setting up a wildcard DNS entry for the domain also pointing to 127.0.0.1 would do the same thing).
Sure enough logon now takes about 5 seconds, even on the Windows 7 machines (which were only taking a minute or so anyway).
Loopback is the best place to point these to, Pointing them to a public server didn't work, and pointing them at a non routeable private IP didn't work either.
To help anyone else confirming this is also the cause of their slow logon issue - when all three conditions are met it's time to mess with your public DNS!
The FQDN of the domain is public (company.co.uk) and not local (company.local).
The DNS servers in use on the network (or the ISP's DNS servers to which DNS requests are forwarded) return placeholder IPs for unknown host addresses, rather than a "non-existent domain or host" error. This can be confirmed by pinging (or doing an
nslookup) on the affected machine, for a host for which no public DNS record exists (ie ping wibble.microsoft.com) - if an IP address is returned then the DNS servers in use are resolving unknown hosts/domains to a placeholder IP.
If you allow the machine to login on the external network, then run a
ipconfig /displaydns you'll see entries for attempts to resolve internal servers themselves, plus lookups relating to the AD domain such as
_msdcs.gc._tcp._ldap.internaldomain.co.uk and such - these shouldn't be there off-domain, and I believe they indicate the machine thinks it's on the domain, even though it isn't.
Hope this helps someone else out.
Ray Von

Setup router to router VPN connecting 2 windows domain networks via 2 RV042 routers

I am using 2 RV042 routers. I have created a point to point VPN with Remote Security Group Type= Subnet, using the default IPSec settings.
Under advanced settings- Aggressive Mode, Keep Alive enabled.
Location A- SBS 2011 standard, Servername=SBSServer, Domainname = Smallbusiness.Local, IP address 10.1.10.50
DHCP range 10.1.10.100 to 10.1.10.175. DNS and Print services. No WINS.
Location B- Server 2008 R2, Sername=SBSServer, Domain name=Smallbusiness.Local, IP address 192.168.10.50
DHCP range 192.168.10.100 to 192.168.10.175, DNS, Print Services and Remote Desktop Services. No WINS
I am wondering 2 things. Can I setup the VPN tunnel to route traffice between the 2 networks without changing the server names. Leaving the servernames the same. I have it setup that way but also had netbios broadcast enable. If I disable netbios broadcast will that be enough for these networks to be independent of each other. I was hoping not to have to rename the domain and there are advantages to having the same user and domain name when mapping drives between networks. I have not needed to authenticate those drives or provide credititals for printing either.
2) Should I change the domain name so that each network has a unique domain name or, if I change the servername of the 2008 R2 server will that essentially solve my network issues, the primary issue being that location b has clients that occasionally can not find the 2008 R2 domain controller. After a restart the usually resolve to the correct domain controller.
Essentially what I am asking is what are the best practices to connect 2 separate Windows domain networks via a VPN and have those networks capable of file sharing to the each others domain server and printing to the network printers at both loations.
Should I have separate domain names-
Should I have separate server and computer names-

"reserved not zero on payload" generally means your pre-shared keys don't match. Try removing the "crypto isakmp key ...." line and retyping it in again on both sides. In particular DON'T cut/paste it from one router config into another, this quite often puts a space character onto the end of the key, which the router interprets as part of the key and they therefore don't match.

SMB Slow connection with upgrade to SnoW Leopard and Windows Clients.

<pre>
Dear,
I have now upgraded my MAC OS X LEOPARD 10,5,8 to new SNOW LEOPARD 10,6,2 and if some problems disappear I have a newer big one !
Now every time a Windows CLient try to connect to a SMB Share of SL server that take a long time about 10-15 seconds to open after that depending on client OS that could be nice for a moment (windows 7 and XP) or browsing stay very slow like for 2003 server connecting to Share on S.Leopard.
Could you please help me.
My SL are the main SMB share computer with all data it is connect like other clients to AD (SBS2003).
I have a SBS2003 server that are Master of Domain
and a Server 2008 acting like Terminal Server also member server of domain.
Here are kind of log I receive from SMBD.LOG: I suppose the Credentials problem when connecting are my explanation but how to avoid that !
2009/11/14 13:37:06, 2, pid=64803 /SourceCache/samba/samba-235/samba/source/smbd/reply.c:reply_special(332)
netbios connect: name1=MACSRV name2=NOMAD
2009/11/14 13:37:06, 2, pid=64803 /SourceCache/samba/samba-235/samba/source/smbd/reply.c:reply_special(339)
netbios connect: local=macsrv remote=nomad, name type = 0
2009/11/14 13:37:08, 2, pid=64794 /SourceCache/samba/samba-235/samba/source/lib/module.c:dosmb_loadmodule(64)
Module '/usr/lib/samba/auth/odsam.dylib' loaded
2009/11/14 13:37:10, 2, pid=64803 /SourceCache/samba/samba-235/samba/source/smbd/sesssetup.c:setupnew_vcsession(1273)
setupnew_vcsession: New VC == 0, if NT4.x compatible we would close all old resources.
2009/11/14 13:37:10, 2, pid=64803 /SourceCache/samba/samba-235/samba/source/lib/module.c:dosmb_loadmodule(64)
Module '/usr/lib/samba/auth/odsam.dylib' loaded
2009/11/14 13:37:18, 2, pid=64803 /SourceCache/samba/samba-235/samba/source/smbd/sesssetup.c:setupnew_vcsession(1273)
setupnew_vcsession: New VC == 0, if NT4.x compatible we would close all old resources.
2009/11/14 13:37:28, 0, pid=64803 /SourceCache/samba/samba-235/samba/source/lib/opendirectory.c:getopendirectoryauthenticator(247)
failed to read DomainAdmin credentials, err=67 fd=15 errno=2
2009/11/14 13:37:28, 0, pid=64803 /SourceCache/samba/samba-235/samba/source/lib/opendirectory.c:opendirectoryuser_auth_and_sessionkey(580)
dsDoDirNodeAuthOnRecordType gave -14091 eDSAuthMethodNotSupported
2009/11/14 13:37:28, 0, pid=64803 /SourceCache/samba/samba-235/samba/source/auth/authodsam.c:opendirectory_smb_pwd_checkntlmv1(387)
opendirectoryuser_auth_and_sessionkey gave -14091 eDSAuthMethodNotSupported
2009/11/14 13:37:28, 0, pid=64803 /SourceCache/samba/samba-235/samba/source/lib/opendirectory.c:getopendirectoryauthenticator(247)
failed to read DomainAdmin credentials, err=67 fd=28 errno=2
2009/11/14 13:37:28, 2, pid=64803 /SourceCache/samba/samba-235/samba/source/auth/auth.c:checkntlmpassword(309)
checkntlmpassword: authentication for user fabrice -> fabrice -> fabrice succeeded
2009/11/14 13:37:28, 2, pid=64803 /SourceCache/samba/samba-235/samba/source/lib/module.c:dosmb_loadmodule(64)
Module '/usr/lib/samba/vfs/darwin_streams.dylib' loaded
2009/11/14 13:37:28, 2, pid=64803 /SourceCache/samba/samba-235/samba/source/lib/module.c:dosmb_loadmodule(64)
Module '/usr/lib/samba/vfs/darwinacl.dylib' loaded
2009/11/14 13:37:28, 2, pid=64803 /SourceCache/samba/samba-235/samba/source/lib/module.c:dosmb_loadmodule(64)
Module '/usr/lib/samba/vfs/notify_kqueue.dylib' loaded
2009/11/14 13:37:28, 1, pid=64803 /SourceCache/samba/samba-235/samba/source/smbd/service.c:makeconnectionsnum(1092)
nomad (192.168.2.20) connect to service NetDown initially as user fabrice (uid=501, gid=20) (pid 64803)
I also have some kind of following message:
2009/11/14 13:35:18, 0, pid=64579 /SourceCache/samba/samba-235/samba/source/lib/utilsock.c:readdata(534)
read_data: read failure for 4 bytes to client 192.168.2.20. Error = Connection reset by peer
NOte that initialy I don't have problem with MAC OS Client but to be sure they use SMB I have desactived AFP server on SNOW LEOPARD SERVER and now they can't browse the share in finder but when connection via COMMAND+K and SMB://server/share that give now the same error but a little bit faster than windows clients.
Could you help me to troubleshout that problem ?
Thanks for your help.
Felee
</pre>

Dear CarlosGBA,
So when you put 2 computers of your network in WORKGROUP in place of DOMAIN the 38 others works fine ? Strange ?
I have about 15 computers, some are already in workgroup other are linux smb other MAC, the data server are MAC OS X SL, the problem appear for all windows machines, I have try to dissable NTLMV2 and Kerberos since it is probably the faulty element with opendirectory,but always without success !
I don't know what I can do to trouble shout, I hope next release 10.6.3 come soon and correct about all SMB problem ! Probably a dream only ! Since I ask my self if Apple want to correct something andwhy is this problem let without solutionso long ! For a company it is a big problem.I suppose that Apple never read this forum and never answer our problem ! May be I should contact the support phone to be helped !
Thanks for you help.

Windows 8.1 Pro Cannot Connect to Domain Controllers through Wi-Fi

I have a domain joined Surface 2 Pro running 8.1 Pro Update that is suddenly unable to connect to the domain controllers on the local network. The machine is fully patched. I'm guessing that it is some network level security issue because the wi-fi is working:
It has no trouble connecting to my Wi-Fi hotspot on my phone.
It has no trouble connecting to other Wi-Fi at coffee shops etc.
It is connecting to my home Wi-Fi and gets an address from DHCP on the domain controllers, but can't ping the DCs, access the DCs through remote desktop even using their IP address.
It can ping the router and ping systems on the internet using their IP address rather than hostname.
I can fully access internet systems if I point it at DNS on the router but still cannot access internal systems by name or IP address.
The Wi-Fi network shows as a public network rather than a domain.
It will work fine when it is docked and using the dock's ethernet adapter.
If I use VPN to loop back through my router then I am able to fully access local systems.
None of the other systems on the network are experiencing the same issue.
I have tried the following which didn't work:
Switched off the Windows Firewall on the Windows 8.1 system and a domain controller.
Network Troubleshooting - which told me that the network seems OK but the DNS servers are not responding.
Uninstalling the Wi-Fi device and restarting the system to re-install it.
Resetting TCP/IP.
I am not aware of any changes, but the system did install System Hardware Update 8/07/2014 (again!) but I can't recall if that was when the problem started or was just a coincidence.
Any suggestions?
Thanks,
Richard
Richard-F

Hi Richard,
Apologize for my slow understanding.
I thought as it could obtain IP address from the DC, it should have connections between them.
For the current situation, you may take a try to disable the firewall on the DC, then check the port that used by AD environment is all available,
Active Directory and Active Directory Domain Services Port Requirements, you could take use of this tool:
PortQryUI - User Interface for the PortQry Command Line Port Scanner
If all available and issue still insists, then issue here seems to be restricted with the wireless router. You may try to contact the router side and see if they could offer any further useful information regarding this situation.
Best regards
Michael Shao
TechNet Community Support

Window 8.1 system unable to access network shares via VPN connection

Is there something inherent to Windows 8.1 that prevents it from accessing shares on a domain?
I know that it cannot join a domain, but does that also mean that it cannot access shares which are on a domain?
My problem is that I have several user that are running windows 8.1 that are connecting to our network via a VPN.
The users have domain accounts but their computers as windows 8.1 cannot joined to the domain.
So to access network shares they have to use their domain credentials to create a VPN connection.
Once connected the user can RDP to systems on the domain using their domain accounts, so I know that their user names/passwords and permissions are correct. They can access these systems using the computer name, so I don't feel that I have a DNS issue.
They can see the shares on our file server, but when they try to access their departments shared file, they receive an access denied message. There are a few shares that are completely wide open, shared to all users and all departments but they cannot access
those shares either.
You can ping the file server, from the the client when they are connected to the VPN but you just cannot access any of the shares.
So...
I am thinking that it has something to do with windows 8.1 and not being able to join a domain, but I cannot find anything to explicitly support this thought.
Other users running a variety different OS (windows 7, OSX, Linux) can all access the shares without any problems via the VPN, so I am a little stumped.

I have done some more testing and oddly enough I can map a drive if I use the IPaddress, but not the computer name, when checking the check box "connect using different credentials"and providing they users domain credentials.
This seems to point to a DNS issue, one would think, but I can hit the file share server by name \\fileserver.dev.lan
I can see all the shares, so dns seems to be fine right?
So I don't understand why I can map a drive using do the IPaddress and not the machine name, but yet I can see and ping the server by name?
When I try to create a mapped drive by machine name I receive the following message:
Windows cannot access \\fileserver.dev.lan\all
You do not have permissions to access \\fileserver.dev.lan. contact your network administrator to request access.
But if I use the \\x.x.x.x\all using the very same user and password I get connected with no problem.
This only seems to happen on windows 8.1, which leads me to think that has something to do with OS.
I am thinking about upgrading to windows 8.1 pro, but I don't want to go though the hassle and expanse is the OS is not the problem.

Windows 10 Build 9926 - Can't connect to this network in certain networks

I have been asked to ask this question here. The original thread can be found at:
http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_web/windows-10-build-9926-cant-connect-to-this-network/e9196f95-5570-4a92-8fae-d29d7d1416b2?msgId=b2246cb5-1038-40dc-98b6-249e8734eb7f
Hello
I have a Samsung 700T tablet.
Since I got the latest update 9926 I am having issues with my corporate network access. I have to type in my user name and password on the wireless connection. When I do I get "Can't connect to this network" message.
I have tried multiple drivers for the network card a "Intel(R) Centrino(R) Advanced-N 6235". I am currently using latest.
I am able to connect fine with my home Wifi.
On the "System" event log I get the following error message when I attempt to login no the WiFi.
"A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 42"
Any ideas?
I have checked and my card is set to use DHCP.
God bless,
Bruno
--- got this answer ----
Have you tried talking to your system administrator? We had a fun bug in our Cisco wireless access points and wireless controller that would
kick Win 8+ machines from even trying to connect. A very long firmware and software update process fixed it.
--- answered back ----
Hello DatAsian,
Thank you for your response.
This is a very large wireless network, and as far that I know I am the only one having this issue. My other devices on the same cube work fine. The only difference is of course Windows 10. The other machines are Windows 8.1 and Windows 7.
In the past this was caused by a driver, but I have gotten about 6 different version of my wireless driver and they all have this issue.
I read on the troubleshoot about entering the wireless configuration manually by using the "Hidden network" screen. The instructions go:
2. Tax or click to connect to a network
3. Tap or click Hidden network tap or click Connect and then enter the network info.
I cannot find this "Hidden network" text on the "Connect to a network" screen. Am I missing something? Do I need to check something that allows me to connect to Hidden network?
One thing that I forgot to mention. I need to enter my user name and password when I enter this wireless network, since this is Employee Own device network.
Any other ideas?
God bless,
Bruno
When I use an android device I had to do the following changes to the way the device connected to wireless:
EAP Method: TTLS
Phase 2 Authentication: PAP
Then I have to use my user name and password.
Is there a way to set windows to the same type of authentication?
Please let me know.
God bless,
Bruno

Hi Alex,
I have the similar problem with Bruno, using the
certificate network.
The Event View show message of the Wired-AutoConfig as below:
Information 1:
Network authentication attempts have been resumed on this network adapter.
Network Adapter: Intel(R) 82579LM Gigabit Network Connection
Interface GUID: {************************}
Information 2:
Wired 802.1X Authentication was started.
Network Adapter: Intel(R) 82579LM Gigabit Network Connection
Interface GUID: {********************}
Connection ID: 0x2
Error:
Wired 802.1X Authentication failed.
Network Adapter: Intel(R) 82579LM Gigabit Network Connection
Interface GUID: {******************************}
Peer Address: ************
Local Address: ************
Connection ID: 0x2
Identity: -
User: -
Domain: -
Reason: 0x70006
Reason Text: The network does not support authentication and 802.1X is enforced in the profile
Error Code: 0x0
Information 3:
Network authentication attempts have been temporarily suspended on this network adapter.
Network Adapter: Intel(R) 82579LM Gigabit Network Connection
Interface GUID: {*************************}
Reason Code: The network does not support authentication and 802.1X is enforced in the profile
Length of block timer (seconds): 1200
everything find with Windows 7 and 8.1
days searching the internet but nothing makes sense.
looking forward to your help
Thanks!

Windows 8.1 laptop not connecting to domain in branch office

We have a problem with a laptop.
It is installed in our Head office (The Netherlands), just like all other laptops by using an image.
Tested and working on the domain.
The user had to go to one of our branch offices (China) and when he connected there, the laptop just won't connect to the domain.
When he plugged in the laptop, it keeps trying to connect it's directaccess.
Other laptops (same image) immediately recognize the domain network, but this laptop just won't.
I am able to ping everything on the local network (MPLS connection), from HQ to all Branch offices but not access them.
I've tried changing the DNS settings, but without any result.
Any suggestions?

Hi,
According to this tool's description, I think it should be helpful to check system current enviroment, such as network, certificates, etc. problem. Actually according to your description, I doubt it probably network enviroment of ISP problem, but we should
find a way to verify our suspect. Then this tool would be convenient, it also would generate a trace log and it would be helpful with troubleshooting.
The DirectAccess Client Troubleshooting Tool is a graphical application, based on the .NET Framework, which checks the health of a DirectAccess client by running various tests. Built-in health tests: The following tests are currently implemented:
Network interfaces Network location (NLS and NRPT DNS) IP connectivity (6to4, Teredo, IPHTTPS, entry point in a multisite setup, DNS) Windows Firewall (applied profile, Firewall outbound rules) Certificates (EKU Client Authentication, trust chain for AIA and
CRL) IPsec infrastructure tunnel (Domain SysVol share) IPsec intranet tunnel (PING and HTTP probes) Additional features Run post-check script (PowerShell, VBScript, BAT or CMD file)
Roger Lu
TechNet Community Support

Satellite U400 - Slow connection on Windows 7

Hi
I use Satellite U400.
And I can't install wireless driver I dont know why. I open the file and it just won't install but still I think I have the latest drivers for my wireless network,
but my serious question was: why I drop and limit bandwith with windows 7 but not with winXP?
I have 1Mbit/s but example I want to download firefox go to their website's and then it shows between 50 and 70Kb/s but sometimes it gets to my normal max high 120Kb/s, and I saw on google that alot of people have this issue.
And sometimes some website are not loading or I just got error because of so slow connection that websites just turn off :(, never happend before.
plz someone help - any suggestions plz?

> what kind of forum is this? no help for more then one 1 week , more then 10 days now ?
What are you expecting? This is a user to user forum if someone would like to help you then he will post in your thread.
In most cases such themes has been discussed a lot of time here maybe you should not wait only for someone but should use an advanced search option and could search and read in similar threads for possible solutions
Regarding your issue:
> i do have the latest updates and still nobody from you tried to help me to get a fix , why dont you guys belive it? when i said look at google.com and write windows 7 wireless probblem or slow down my wireless, this is a KNOWN issue with windows 7 .
Firsty you said that you are sure it's Win 7 issue
>i have asked around everywhere and they all say it is NOT windows 7 issue it must be the manufacter driver issue .
Now you are saying it;s notebook issue....
So what is your possition now????
How it could be a manufacturer issue if the speed is faster using WIn XP??? For me it make no sence...
However, I googled a little bit an found this:
Tweaking Windows 7 for Faster Online Connections
http://www.brighthub.com/computing/windows-platform/articles/58522.aspx
You can also try to speed up the IE 8
For that use the command: regsvr32 actxprxy.dll
This should be typed in RUN
Then reboot the notebook.

Windows 8 PC Slow Connection to Domain Network

Similar Messages

Maybe you are looking for