Slow connection to OSX Server 10.6

Running 10.6.5 server on 10.6.5 clients.
Anyone notice how slow it can be to connect when using the shortname for the username?
If you connect using the long name it's instant? Any ideas?
This is file sharing using Open Directory.

I am also finding authenticating against osx server / directory or workgroup manager very slow. When I login to a Network Account it takes several minutes.

Similar Messages

Newbie: Connect Windows - OSX Server

Hi
I'm completely new with osx server. Installed it 5 min ago
I'm wondering how i manage to get a remote desktop connection from a windows machine to the osx server?
If i try on the windows the remote desktop with the IP of the server it can't connect.
By the way, how to i manage to get a remote connection from mac to mac server?
Thx

I would politely disagree. Yes, definitely, the Mac 'Screen Sharing' app works a treat, and Apple Remote Desktop.app works as well, but I am coming from a Window's PeeCee.
For me, connecting to my 10.5(.8) Server via tightvnc gives 'Server did not offer supported security type!". Using RealVNC to this machine states "No matching security types Do you wish to reconnect to ... ?" a telnet to this AppleVNCServer service (port 5900), shows RFB 003.889 *, or Remote Frame Buffer Major 3, minor 889.
Also, connecting to multiple 10.6(.1) Clients with Tightvnc correctly asks for a password but then hangs at "Status: Security type requested". Using RealVNC opens, connects, asks for authentication, and exits. Telneting to this AppleVNCServer service (port 5900), also shows RFB 003.889 *.
The Current Version of the protocol is supposed to be 3.8, that is Major version 3, minor version 8. Not 80 or 800 but Eight). http://www.realvnc.com/docs/rfbproto.pdf and I believe that tightvnc only supports up to version 3.7.
On each station I have installed the 'old' OSXVnc.app as a service (to a unique port). OSXVnc utilizes protocol 3.3 and I can control them successfully, but that is of my own doing because of this issue.
Now JollysFastVNC works a treat to any machine I have EVER tried to connect to. I have not tried COTVNC or any of the others (too slow for me, when they wer e around)
Also, I just noticed that RealVNC states that their free and personal version will not connect to Mac OSX (x86 and PPC) but the Enterprise one will. I just Dl'ed the Enterprise Viewer and it gave essentially the same thing ('protocol is not valid' message, even after it asks for a password). Anyway, I am not here to hijack this thread, just trying to keep the info flowing and open.
Maybe I am the only one with these problems but the bottom line is I cannot use Real or Tight, or UltraVNC to administer my server or clients as long as AppleVNCServer gives out the 003.889 protocol version.
Peter
* The ProtocolVersion message consists of 12 bytes interpreted as a string of ASCII characters in the format "RFB xxx.yyy\n" where xxx and yyy are the major and
minor version numbers, padded with zeros.

Outlook doesn't want to connect with OSX Server on 2 out of 3 clients

I have three computers on which I have installed Outlook 2011. All three are running Mavericks. On one of them, a MacBook air, I have established an outlook account connecting to my OSX server with no problems. On the other two computers when I set the parameters the same way, I cannot establish an outlook account. When I use Apple Mail on any of the three machines, I am able to establish accounts for iCloud and the OSX server with no problems. Can anyone point me to the source of this problem or a method for trouble shooting it?

Hi tommy-ch,
Apa kabar,
Do visit and post your thread in boot camp discussion:
http://discussions.apple.com/forum.jspa?forumID=1165&start=0
There are more experience user on bootcamp that might gladly help you out.
Good Luck.

Cant connect to OSX server over network in recovery mode

Hi guys.
First of all, thanks for any help you can give me.
I am running osx server on a mavericks mac mini on a home network. Attached to it I have a 1tb hard drive to which all the macs in my house use time machine to back up over my network and they are stored there.
I have just formatted one of my macs and want to restore it from these time machine backups that are on the osx server on my network.
When i enter recovery mode from boot (COMMAND R), it can see the "backups" on networks "Matts-Mac-Mini" but when i then click "CONNECT" it says "Enter your name and password for the server "Matts-Mac-Mini/local" so that Time Machine can access it.
It gives me a box with NAME and PASSWORD and a CONNECT button.
By DEFAULT the "NAME" it starts with is "root".......which I dont understand.
I have tried every single iteration of names and passwords I can think of but it still wont connect, it either shakes the box or gives an error saying "There was a problem connecting to the server "Matts-Mac-mini.local". Check the server name of IP address and then try again".
I have tried the log in details for the osx server, the login details for the mac im trying to connect from, used root as the username, tried capitals, no capitals, spaces no spaces etc. I am at a total loss and about to tear my hair out!!
Is there anyone able to give me any help with this please, I would be SO grateful!
Many thanks,
hardtofin

I think I have isolated the password, with a certain username and password the box never shakes and instead gives the error: "There was a problem connecting to the server "Matts-Mac-mini.local". Check the server name of IP address and then try again".
Are you able to offer any help with this? I dont see why i can't connect to it, if the imac can already see it?
Many thanks again,
hardtofin

Trouble connecting to OSX server from XP domain members

Can someone help me out with a problem connecting to our OS X server from Windows XP? Basically, I only have trouble connecting from XP machines that are members of the domain.
Here are some details:
OS X Server 10.3.9, bound to domain through Active Directory.
Windows Services role = Domain Member.
Computer name (under Windows Services) = macserver
Connects fine from Macs via Network>Domain>macserver
macserver IP address: 192.168.1.5
Sharing 1 folder to all members of the domain.
I can connect fine from OS X computers and XP computers that are NOT members of the domain
I can connect from XP domain members via the IP address \\192.168.1.5
I cannot connect from XP domain members via Network Neighborhood>Domain>macserver, or by entering the computer name. Error message recieved: "The account is not authorized to log on from this location."
I can ping macserver from any xp machine and it resolves the IP address.
I can browse the webserver on OSX Server via http://macserver.
Any thoughts?
Thanks,
Eric
PowerMac G4, MDD Mac OS X (10.3.9)
PowerMac G4, MDD Mac OS X (10.3.8)

I can't remember how I resolved this. I think I had a number of problems, for instance, spaces in fileshare names. I might also have set up the domain incorrectly. Who knows.

Slow connection in one server if accessing through Cisco ACE

Hi,
Good day, Can someone help me on my problem? I have 3 servers, server1, server2 and server3. When one pc accessing the server 3 application via Cisco ACE, it experienced a slow connection but when direct access without Cisco Ace, it's fast. The connection of this PC through cisco ace and direct access have no issue.
What need to do in my configuration? Below is my configuration
logging enable
logging timestamp
logging trap 7
logging buffered 7
logging monitor 7
logging host 167.81.126.5 udp/514
logging host 137.55.152.147 udp/514
resource-class SG_01
limit-resource all minimum 0.00 maximum unlimited
limit-resource sticky minimum 10.00 maximum equal-to-min
boot system image:c4710ace-mz.A3_2_0.bin
login timeout 30
peer hostname singapore-ace2
hostname singapore-ace1
interface gigabitEthernet 1/1
channel-group 14
no shutdown
interface gigabitEthernet 1/2
channel-group 14
no shutdown
interface gigabitEthernet 1/3
channel-group 14
no shutdown
interface gigabitEthernet 1/4
channel-group 14
no shutdown
interface port-channel 14
description ISOLAN-ACE-TRUNK
ft-port vlan 99
switchport trunk native vlan 1
switchport trunk allowed vlan 12,14,112
no shutdown
clock timezone SGT 8 0
ntp server 137.55.152.1
context Admin
member SG_01
access-list ALL line 8 extended permit ip any any
access-list ALL line 9 extended permit icmp any any
ip domain-name ysn.psg.philips.com
probe http singapore_01
description This probe used to monitor application url-app-script
interval 5
passdetect interval 5
request method get url /insiteserverstatus/insiteserverstatus.aspx
expect status 200 200
open 1
probe http singapore_02
description This probe used to monitor IIS-login-page
interval 5
passdetect interval 5
request method get url /InSiteLumiledsApplication/
expect status 200 200
open 1
probe icmp uplink
description This probe used in conjunction with ft track host
interval 2
faildetect 2
passdetect interval 3
parameter-map type connection PARAM_L4STICKY-IP
exceed-mss allow
rserver host sggysnysn1ms013
ip address 137.55.152.135
inservice
rserver host sggysnysn1ms014
ip address 137.55.152.136
inservice
rserver host sggysnysn1ms018
ip address 137.55.152.145
inservice
serverfarm host PLI9058
probe singapore_01
probe singapore_02
rserver sggysnysn1ms013
    inservice
rserver sggysnysn1ms014
    inservice
rserver sggysnysn1ms018
    inservice
sticky ip-netmask 255.255.255.255 address both SG_GROUP_01
timeout 720
replicate sticky
serverfarm PLI9058
class-map type management match-any HTTPS-ALLOW_CLASS
class-map match-all L4STICKY-IP_141:ANY_CLASS
2 match virtual-address 137.55.152.141 any
class-map type http loadbalance match-any NO_MS018
50 match source-address 137.55.155.31 255.255.254.0
class-map type management match-any SSH-ALLOW_CLASS
2 match protocol ssh source-address 167.81.124.0 255.255.255.192
3 match protocol ssh source-address 167.81.126.0 255.255.255.192
class-map type management match-any remote_access
2 match protocol xml-https any
3 match protocol icmp any
5 match protocol ssh any
6 match protocol http any
7 match protocol https any
8 match protocol snmp any
policy-map type management first-match remote_mgmt_allow_policy
class remote_access
    permit
policy-map type loadbalance first-match L7PLBSF_STICKY-NETMASK_POLICY
class class-default
    sticky-serverfarm SG_GROUP_01
    insert-http X-Forwarded-For header-value "%is"
policy-map multi-match PLI9058-VIPs_POLICY
class L4STICKY-IP_141:ANY_CLASS
    loadbalance vip inservice
    loadbalance policy L7PLBSF_STICKY-NETMASK_POLICY
    loadbalance vip icmp-reply
    connection advanced-options PARAM_L4STICKY-IP
interface vlan 12
description Client-side vlan
bridge-group 1
no normalization
mac-sticky enable
access-group input ALL
access-group output ALL
service-policy input PLI9058-VIPs_POLICY
no shutdown
interface vlan 14
ip address 137.55.152.236 255.255.255.248
peer ip address 137.55.152.237 255.255.255.248
service-policy input remote_mgmt_allow_policy
no shutdown
interface vlan 112
description Server-side vlan
bridge-group 1
no normalization
access-group input ALL
access-group output ALL
nat-pool 1 137.55.152.141 137.55.152.141 netmask 255.255.255.192 pat
no shutdown
interface bvi 1
ip address 137.55.152.189 255.255.255.192
alias 137.55.152.188 255.255.255.192
peer ip address 137.55.152.190 255.255.255.192
description Bridge-Group 1 Virtual Interface
no shutdown
ft interface vlan 99
ip address 192.168.1.1 255.255.255.252
peer ip address 192.168.1.2 255.255.255.252
no shutdown
ft peer 1
heartbeat interval 100
heartbeat count 10
ft-interface vlan 99
ft group 1
peer 1
priority 150
peer priority 50
associate-context Admin
inservice
ft track host test1
track-host 137.55.152.234
peer track-host 137.55.152.235
peer probe uplink priority 50
probe uplink priority 50
ip route 0.0.0.0 0.0.0.0 137.55.152.233

Hi Earsdale,
All the three servers are using the same configuration, so, I'm afraid it's not possible to give you a simple answer. You will need more troubleshooting.
I would recommend you to start by checking the differences between the servers because one of those differences is certainly causing the failure.
Also, it would be helpful to get traffic captures on the TenGig interface of the ACE to compare the behavior of the connection when going to the different servers, as well as the differences when being load-balanced vs accessing the server directly.
If you need help with this troubleshooting, you can always open a TAC service request
Regards
Daniel

Connection to OSX Server delayed - no auto connect

when I try to connect to my OSX server it takes around one minute before the connection is established . every morning I have to reconnect with the server (no auto connect). the other two MBP in the office with OSX 10.5 are auto connected every time.
MPB OSX 10.6.2
Server OSX Server 10.5.8
connected over ethernet

Under the Apple Menu ->System Preferences ->Network. The left hand column should display known network connections. Click the little plus sign and add the appropriate connection.
For future reference this information is available via the help menu as are directions that might be easier to understand.

IChat LAN-LAN bonjour connection via OSX-Server and Draytek routers ?

We want to configure a LAN-LAN iChat intranet connection via our OSX-Server and several Draytek 2600 routers. We have static IP-addresses in all local LANs, do LAN-connection via DynDNS and opened the iChat NAT-Ports on every router as described in several posts.
LAN-LAN connection (e.g. volume mounting and ARD (Apple Remote Desktop)) works fine. We started iChat on every Mac and chatting via .mac accounts also works, but not via Bonjour. The logged-in users are not listed in the iChat bonjour contact list.
What do we have to configure more ? Starting the iChat service on the OSX-Server ?
Thanks in advance for help
Alex
PowerPC G5 DP 1.8MHz Mac OS X (10.4.9) 1GB RAM 22 Display
PowerPC G5 DP 1.8MHz Mac OS X (10.4.6) 1GB RAM 22 Display
PowerPC G5 DP 1.8MHz Mac OS X (10.4.6) 1GB RAM 22 Display

Bonjour works without a server but will only work within the same subnet. It's likely your routers are on different subnets and so using Bonjour you would only be able to see contacts on the same subnet.
If you're not seeing anybody else at all, even those on the same subnet as you, then perhaps your firewall hasn't been opened to the iChat Bonjour ports (TCP, 5297 and 5298). There's also an entry for it in each Mac's Firewall config pane.
You best bet may be to run an XMPP server. iChat server is an XMPP/Jabber server (using a copy of the pretty old Jabberd 1.4 code), but you might want to consider running the superior OpenFire (http://www.igniterealtime.org/projects/openfire/index.jsp) on your server instead.
Just create all the users on the server and then enter the relevant details into each copy of iChat.

SMB connection attempt switches to WebDAV unexpectedly when connecting to OSX server

With Windows 8.1, I can connect to my OSX 10.9.5 Server share point by opening File Explorer, typing: \\<fqdn> and hitting return. I will be prompted for server credentials and when I enter them, I will see the share point.
With Window 10, if I do the same thing, instead of seeing the shareppoint, I see a blank Windows Explorer screen with "This folder is empty".
I contacted Apple with a tcpdump from this and they said that Windows 10 is attempting to connect over HTTP instead of SMB:
ACTION: Windows is handling the connection incorrectly by attempting to use Webdav instead of SMB.
STATUS: As with any other 3rd party integration cases, we attempt to identify an issue as either an issue to a 3rd party product, or to identify and isolate the issue in
the Apple product.
In packet 64 the client sends an SMB 1 negotiate request (expected).  In packet 66 the server responds in SMB 2 with the SMB 2 features it supports
(expected).  In packet 67 the client sends the SMB 2 negotiation request (expected).  In packet 69 the server responds with the SMB2 negotiation response (expected).
Normally at this point the client will send an authentication attempt in SMB 2 using one of the authentication types provided by the server in packets 66 or 69.  Instead
the Windows client sends a tcp connection reset in packet 70 (unexpected).  In packet 74 the windows client initiates a connection over HTTP (extremely unexpected).
The above pattern repeats several times in the tcpdump.
The mac server never presented any HTTP information in the SMB packets.  This appears to be a purely Windows 10 issue.
If I connect to the server by typing: \\<fqdn>\sharepoint -- then I do connect, but the OSX server does not indicate this is an SMB connection, so it must be a WebDav connection (which would be incredibly wrong...)
If this is a settings issue in Windows 10 that is forcing an HTTP connection over an SMB attempt -- can somebody point me where to look?

On Thu, 20 Nov 2014 17:04:11 +0000, steve maser wrote:
According to Apple, it appears that if the SMB server (in this case Mac OS X 10.10.1) has port 443 open, Windows 10 attempts to connect over that instead of over the SMB port.
Anybody looking at this one?
If you want someone to look at this you need to file it using the Feedback
tool, if you haven't already done so.
Paul Adare - FIM CM MVP
Actually, we have scientifically determined that Heisenberg did indeed
sleep exactly here. However, we have no idea whatsoever just how fast
asleep he was. -- Dave Aronson

Win7 clients can't connect to OSX Server after 10.10.2 and Server 4.0.3 update

I'm troubleshooting an annoying issue with our Yosemite fileserver at work and hoping someone has suggestions.
The server is running Yosemite, clients a mix of MacOS from 10.6 through 10.10, and some Windows 7 boxes.
With the server on 10.10.1 and the just-prior version of Server (4.0, I assume; were 4.0.1 and 4.0.2 ever available to the public?), everything basically worked. Last night, I updated the server to 10.10.2 and 4.0.3. Nothing unusual during the update apart from a bunch of spotlight indexing processes running as individual users sucking up a lot of CPU for the first few minutes, which may be normal.
However, now almost all the Macs are fine, but the Windows clients are all getting permissions errors when trying to connect. Even weirder, one Yosemite client was also getting an error on login when trying to connect via SMB, both on 10.10.1 and 10.10.2; the same computer connecting via AFP works fine.
I'm inclined to think that it has something to do with the switch to SMB3 mentioned in the changelog for Server 4.0.3, although I'm not 100% sure that didn't exist under 4.0 as well, and if this is the problem I'm not sure what to try to fix it.
I'm already aware of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\LmCompatibilityLevel needing to be at least 3 (or non-existent, so it defaults to 3 on Win7) to work with Yosemite; these clients already have that registry key set. Suggestions?

Addendum: I just realized that the Windows users *can* see their own home folder when they connect to the server without the main share I'm trying to mount specified. So it's not that they're completely unable to connect, it's just that the server isn't offering them any of the main share when they do.
When I tried mounting the server from 10.6 manually forcing SMB (with an admin user, no less), I got the same thing--just my user folder, none of the main shared volumes...

Connecting to OSX Server VPN

Hello-
I have a machine running OSX.4.9 server. When I had it connected to a Linksys Router with VPN pass through it works flawlessly. I moved the server to a remote location and deployed a ExtremeN device as the router. I can talk to the Server, but I cant authenticate. It seems like user information is not being passed. Here is what is happening when the Client touches the server box.
Jun 27 12:45:37 -Server vpnd[39]: Incoming call... Address given to client = 192.168.1.56\n
Jun 27 12:45:37 -Server pppd[29992]: pppd 2.4.2 (Apple version 233-0-4) started by root, uid 0
Jun 27 12:45:37 -Server pppd[29992]: PPTP incoming call in progress from '216.228.X.X'...
Jun 27 12:45:37 -Server pppd[29992]: PPTP connection established.
Jun 27 12:45:37 -Server pppd[29992]: Connect: ppp0 <--> socket[34:17]
Jun 27 12:46:07 -Server pppd[29992]: LCP: timeout sending Config-Requests\n
Jun 27 12:46:07 -Server pppd[29992]: Connection terminated.
Jun 27 12:46:07 -Server pppd[29992]: PPTP disconnecting...\n
Jun 27 12:46:07 -Server pppd[29992]: PPTP disconnected\n
Jun 27 12:46:07 -Server vpnd[39]: --> Client with address = 192.168.1.56 has hungup\n
Jun 27 12:46:43 -Server vpnd[39]: Incoming call... Address given to client = 192.168.1.57\n
Jun 27 12:46:43 -Server pppd[157]: pppd 2.4.2 (Apple version 233-0-4) started by root, uid 0
Jun 27 12:46:43 -Server pppd[157]: PPTP incoming call in progress from '216.228.X.X'...
Jun 27 12:46:43 -Server pppd[157]: PPTP connection established.
Jun 27 12:46:43 -Server pppd[157]: Connect: ppp0 <--> socket[34:17]
Jun 27 12:47:13 -Server pppd[157]: LCP: timeout sending Config-Requests\n
Jun 27 12:47:13 -Server pppd[157]: Connection terminated.
Jun 27 12:47:13 -Server pppd[157]: PPTP disconnecting...\n
Jun 27 12:47:13 -Server pppd[157]: PPTP disconnected\n
Jun 27 12:47:13 -Server vpnd[39]: --> Client with address = 192.168.1.57 has hungup\n
Any suggestions would be appreciated.
Mac OS X (10.4.9) Server

I am trying to figure this out also.. I've had no luck

SUPER SLOW connecting with PC server

I have three G4 Power Macs that are now connecting to a Dell Poweredge 2900 PC server. Trying to open files across the network from this server is EXTREMELY slow. A PC connected to this same configuration opens the files just fine. The files to be opened are Mac originated Quark and Adobe CS2 type files and range from small (200K) to Huge (100M). Even the tiny files take a long time.
What can I do to speed the connection?
What's the best way to have Mac files on a server and also automatically backed up to this PC server's tape drive? The information on the server is (and needs to be) backed up to a tape each night.
We also have noticed that files are duplicating themselves (sometimes) when saved to this server. Any ideas on why that is happening?
Thanks so much for your help!

Janet –
Are you on Tiger or an earlier version of OS X? Though most are not thrilled at the prospects of upgrading an OS, Tiger does play much better with Windows and I would recommend that OS as a minimum for connecting to a Windows environment. With that said here are some other things to try –
- Open a ‘Terminal’ session on your Mac and check the response times between your Mac and Server <ping –s 4096 xxx.xxx.xxx.xxx> where xxx.xxx.xxx.xxx is the server IP. If your response times are greater than 2 ms then the problem could lie in your physical network. As a check I would run the same from a PC <ping xxx.xxx.xxx.xxx –l 4096>
- On the file server if enabled I would turn off (temporarily) any A/V and or firewall software you may have installed. (You may want to disconnect Internet access to your network when trying this test).
- Try/what happened when you move files between the Macs?
Also are the Macs in the Domain? Finally – I am not sure that MacDrive will solve your problem. It is primarily designed to allow PC’s to see Mac drives as Windows drives. Though I am not suggesting that it would not work I just think that your problem has more to do with server or network configuration.
One last thing I did a little checking you your Server and noticed that it is a dual NIC system. Are the NICs configured for failover? If so can you disable failover and then disable one of the NICs and see what happens? Also as this is a server I assume that the server has a static address as well? You may also want to assign your Mac static IPs as well – make sure to include both the DNS server as well as the WINS server (if installed) when configuring your IPs on the Macs.
Hope this helps –
BH

Limited number of 5 concurrent VPN (ipsec/l2tp) connections to OSX Server

We've configured OS X 10.6 Server on XServe to accept VPN connections either via PPTP or via IPSEC/L2TP using a PreSharedKey.
When multiple clients try to connect using IPSec/L2TP, we experience problems as soon as 5 users are connected. No additional ipsec/l2tp connections can be created until one of the 5 existing connections is terminated, but then a new connection can start immediately.
Sniffing with tcpdump, the following can be seen on the server side:
09:24:45.349541 IP clientIP.isakmp > serverIP.isakmp: isakmp: phase 1 I ident
09:24:45.354978 IP serverIP.isakmp > clientIP.isakmp: isakmp: phase 1 R ident
09:24:45.358233 IP clientIP.isakmp > serverIP.isakmp: isakmp: phase 1 I ident[E]
09:24:45.365359 IP serverIP.isakmp > clientIP.isakmp: isakmp: phase 1 R ident[E]
09:24:45.367222 IP clientIP.isakmp > serverIP.isakmp: isakmp: phase 2/others I oakley-quick[E]
09:24:47.365936 IP clientIP.isakmp > serverIP.isakmp: isakmp: phase 2/others I oakley-quick[E]
09:24:50.365799 IP clientIP.isakmp > serverIP.isakmp: isakmp: phase 2/others I oakley-quick[E]
The last lines are repeated several times, until the connection attempt times out.
When using PPTP connections, we don't experience these problems, and in addition PPTP connections can even be created when 5 ipsec/l2tp connections are already established.
Does anyone know if there is some kind of limitation for the number of concurrent ipsec/l2tp connections built into OS X server? So far, we have not seen anything like this in the docs.

Ok, IMAP server almost universally allow multiple connections. Thunderbird as you would have observed uses 5 if they are available. As Airmail suggested, iphones just use more and more until they exhaust the available connections. There is no set maximum option.
However there are other things that can consume connections and some may surprise you.
Anti spam tools such as mail washer
Anti virus programs in their anti spam or anti phishing roles
Web mail.
The wife sharing the same account on her laptop.
That is from the top of my head. So could any of those apply.

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.

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.

Slow connection to OSX Server 10.6

Similar Messages

Maybe you are looking for