slow access & remote desktop error with 2008 server

We have a 2003 SBS Premium server running ISA 2004 SP3 and we installed a new 2008 server as a backup domain and file server for our business.

Everything is setup and working, but if I run anything off of a shared folder from the 2008 server it delays for about 20 seconds and sometimes it will time out if I access it from the 2003 server. We are also getting an issue with remote desktop trying to access the 2008 server that the user id or password is incorrect. I know that not to be the case and I am stuck as to what I should do to troubleshoot these issues.

I checked the dns and do not see any issues. I tried entering a rule for the new server just to make sure ISA wasn't blocking it and that didn't help either. I also installed an update package that was supposed to fix issues similar to these and nothing changed. I have checked everything I could find on the support pages. What should I do at this point to troubleshoot this?

 

Hi guitar8222

Clarify:

Is this delay only via RDP or local using explorer etc? If local then of course it will be there in an RDP session.

The RDP you are referring to is I assume outside on the WAN coming in.

If so do you get same issues with RDP from a station accross the LAN?

Mike

 

The delay is on the lan from local clients and the server. If we run the program from our 2003 server it loads instantly and the 2003 server is spec'd a lot lower than the 2008 server. They both are on gb switches.

The RDP error happens locally. The server is on local network hidden behind the NAT and I haven't tried giving it an external static ip. I get the log in screen, but it just won't verify the user name or password.

The 2003 server is providing the DHCP, DNS, WINS, and AD services along with the ISA server. I am at a loss and would be very grateful for any ideas of what I should do.

 

OK you are not giving me muuch to go on so lets get some ammo!

Go to Svr2K8 log off!

Log on a user that has this issue from his/her workstation let them test App from the Svr2K8 console!

Does it have the same delay?

Do same from Svr2k3 any difference?

Now go to a workstation create a matching Administrator account as is on the 2 servers. Log in and test using this account!

Mike

 

I get the same slowness on any of the clients. The app only runs fast on the 2008 server itself. I can't login to the server through RDP with any admin user account from any computer. It won't authenticate a login with any of them.

I just found an error on the 2003 server from isa that reads the published RPC service at 192.168.16.4:135 (address of the w2k8 server) can not be reached. And then another one that it was restored. So I guess I need to troubleshoot isa now? Could it be a simple rule even though I set a rule to allow all traffic through from the local network to the 2k8 server?

 

Reggie posted this I can't say it better so go thru it post back your results
http://windowsbbs.com/showthread.php?t=67193

Get us this info:

Drag your mouse to highlight the below, between the lines then rt click and copy.
--------------------------------------------
%SystemRoot%\system32\cmd.exe /c %windir%\system32\ipconfig.exe /all >> "%USERPROFILE% "\Desktop\Ipcfg.txt
--------------------------------------------

Do one for server then one from a workstation.

Then do the below one from workstation to server (fill in computer name) and one from the server to the same work station.

Paste below to CMD prmt one line at at time then post the file it creates on desktop.

On workstation
pathping computername of server > "%USERPROFILE% "\Desktop\pathping.txt
pathping lan ip of server >> "%USERPROFILE% "\Desktop\pathping.txt

On Server
pathping computername of workstation >> "%USERPROFILE% "\Desktop\pathping.txt

pathping lan ip of workstation >> "%USERPROFILE% "\Desktop\pathping.txt

The rsults of these will appear on the desktop post them back xx.xxx out some of the IP's but not the first 3 example 208.xxx.xx.xx.

Mike

 

Windows IP Configuration

Host Name . . . . . . . . . . . . : xxxxxxserver
Primary Dns Suffix . . . . . . . : XXXXXXXXX.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : XXXXXXXXXX.local

Ethernet adapter Server Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #2
Physical Address. . . . . . . . . : 00-30-48-59-65-15
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.16.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.16.2
Primary WINS Server . . . . . . . : 192.168.16.2

Ethernet adapter Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-30-48-59-65-14
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 70.xx.xx.xxx
Subnet Mask . . . . . . . . . . . : 255.255.255.248
Default Gateway . . . . . . . . . : 70.xx.xx.xxx
Primary WINS Server . . . . . . . : 192.168.16.2
NetBIOS over Tcpip. . . . . . . . : Disabled


This is the ip config for the 2003 server. I can't run it from the 08 server until tommorow since I can't remote desktop. I also found out that I can't remote desktop to a vista client, so at least I know that is just a config issue.

I ran the pathping to the w2k8 server and it showed 0 packet loss with the ip address and the name of the server. Again tommorow I will see what the opposite direction shows and I will run it from a few clients too just to check.
With pathping going to the 2008 server it showed 0 packet loss.

 

???

Where is this Server is it not on the local area network?

Why 70.xx.xx.xx Ip and Gateway???????? Are you really pulling DNS from the WAN (Internet)???

Which is the primary DNS server 2k3 or 2k8??

I'm lost!

Mike

 

Forget RDP for now!

Concentrate on getting DNS correct and RDP will likely work!

How many routers are we going thru and is any of them enabled to provide DHCP?

Mike

 

The 70 address is our static Ip from comcast. We use this port for our mx and remote webmail, etc... The server has two network ports. The 70 address runs right to the modem and the 192.168.16.2 is connected to the switch. This is the 2003 server which provides the dhcp, dns, etc for the lan. The 192 address is pointed to itself for lan dns replication and the 70.xx.xx.xx port is configured as wan access.

The only machine setup as a router is the 2003 server. Everything is connected by a 10/100 & 2 port x1000 switch. Our comcast buisness modem is just set up to provide passthrough and doesn't assign dynamic addresses.

The 2008 server has an assigned address of 192.168.16.4 on the lan with only one port and doesn't have a direct connection to the internet.

Does that make sense?
I am pretty sure our dns is correct. I know that everything should be setup correctly and sbs server 03 by default can setup the ports and dns in the same manner.

On a side not, thanks for posting that link to the other post. I didn't realize that there was an advanced active directory menu that was hidden. I was wondering where the AD DNS settings were hidden. However, everything appears to be correct.

I won't be able to have access to the 2008 server until tommorow or monday due to my wife having a medical emergency. I probably wont be able to respond on here, but so far I wanted to thank you for the help.

 

I was sent this solution, which I will try tommorow. I think this may be the issue that I was running into. I still don't know about the remote desktop problems, but I have my fingers crossed. I don't really know about Sever Message Block and the differences between versions, but I think this may be the solution. What do you think about it?


For slow access from window server 2003 to 2008, you can refer to the methods below to test the result:

1)Please check if your Windows Server 2008 is the latest version (RTM).

You can locate the
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version] registry key. There is a subkey which contains the Windows build information. 6.0.6001.18000 means RTM version. If not, please upgrade to RTM version.

2) Windows Server 2008 uses Server Message Block (SMB) 2.0 for file access, while windows server 2003 uses SMB 1.0. It might lead to incompatible problem and cause slow access. You can refer to the following steps to force Windows Server 2008 to use SMB 1.0 for file access.

Please note that this workaround will change the registry and, serious problems might occur if you modify the registry incorrectly. It's just for the test and you should back up your registry before taking any steps below. Additionally, this will turn off SMB 2.0 communications when sharing all files.

1. On the server that you shared your files, click Start, click Run then type Regedit and press Enter.
2. Locate and select the key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
3. On the Edit menu, point to New, and then click DWORD (32-bit) Value. Name this value "SMB2" without the quotation marks.
4. Select the SMB2 value. If the value is not 0 (zero); on the Edit menu, click Modify. Change the Value data to 0 (zero) and click OK.
5. Reboot the computer.
=====

For Windows server 2008 Terminal server issue, please check if the user you attempt to logon TS exists on the Windows server 2008.

What is exact error message word by word in Event Viewer? If you use administrator account, does this issue still persist? Please also check if you enable 'Remote access' in Remote setting of computer properties?

What's more, the corruption of trust relationship between the client and domain server also causes the similar issue. Please test to disjoin this client and rejoin it into domain to test the result. More information, please refer to:

"System Cannot Log You On to This Domain" Error Message

http://support.microsoft.com/kb/810497/en-us