SBS 2003 with additional terminalserver and additional dwh-server

I have the following problem:

Configuration:
SBS-Server 2003 Premium with SP2 and all updates (exept IE7), no
ISA-Server installed
Intel Xeon 3.6 Ghz, 4 GB RAM, 3 x SAS-Harddisk 140 GB RAID-1 + Standby, 2
x 1 GB-Nic teaming on redundance , rackserver
working since 08/2006
function: SBS-Server, Exchange, SQL-Server, Fileserver, DHCP, DNS, WINS <SBS>

second server with Windows Server 2003 R2 Terminalserver with SP2 and all
updates (exept IE7)
Intel Xeon 3.6 Ghz, 4 GB RAM, 2 x SAS-Harddisk 140 GB RAID-1, 2 x 1
GB-Nic teaming on redundance, rackserver
working since 08/2006
function: Terminalserver for 25 Clients, memberserver <WTS>

third server with Windows Server 2003 R2 with SP2 and all updates (exept IE7)
Intel Pentium Dual Core [email protected] Ghz, 4 GB RAM, 2 x SATA-Harddisk 150 GB
RAID-1, 1 x 1 GB Nic, no rackserver
new since 25.01.2008
function: data-ware-house-Server with Palo-Excel Plugin,
memberserver <DWH>

Network:
Level-One Gigabit-Switch 16 Port, length of cable 2 m, all server gigabit,
ip-addresses in same C-class (192.168.120.1, 192.168.120.2 und 192.168.120.3)

the problem:
any connection from <SBS> to <WTS> and back (i.e. UNC-name\c$)
very fast
any connection from <SBS> to <DWH> and back (i.e. UNC-name\c$)
very fast

any connection <WTS> to <DWH> (i.e. UNC-name\c$) is either very slow or
errormessage
"Access denied. Contact your administrator for further information. The
network path was no longer found."

Both server are memberserver of the sbs-domain, and DNS- and WINS-server
point to the sbs-server. If I PING the server each other or from the
sbs-server i receive answers with the full-qualified name of the servers.
ipconfig /displaydns shows, that the names are found
if I try a connection with the ip-addresses (\\192.168.120.2\d$) same problem.

What I did, to solve the problem:

I removed the new server <DWH> from the domain, then I joined the domain
again with the sbs-wizard ... problem still here
on the server <DWH> I did:
ipconfig /flushdns
ipconfig /registerdns
checked later with ipconfig /displaydns, all ok
but my problem is still here
checked wins-db and dns: all entries ok

My question: any tips, what to do next ? Are there known problems with sbs
2003 and additional servers ?

Greetings and thanks in advance for any help

Andy

 

Thank you for your answer

When I ping the ts from sbs by name it responds with correct ip, when I ping
the dwh-server from the sbs by name, it respond with correct ip, when I ping
the sbs from ts or dwh by name all ok, and also when I ping the dwh from ts
or ts from dwh all ok, always respond with full qualified name.

why do you think I should disable the teaming, working since 08/2006 in both
servers, sbs and ts perfectly ?

thank you in advance

 

All working with domain accounts, all situiation with domain-admin-account
The ts was not connected with the sbs wizard, the dwh was connected with the
domain wizard

my problem on swiching off the teaming is, that all the servers are located
at the ISP, I don't have a DHCP-Server, so I think when switching off the
teaming, I will lose all connection to the TS. My LEVEL ONE Switch is
managable, I don't see any errors or duplicate packets on the ports

 

The dwh-server is 2 weeks old. What I don't understand is, that the
dwh-server can perfectly connect to the sbs server, but not to the ts. The
problem is from the beginning.

 

Thank yout Thomas for your reply:

there is no firewall software installed on any server
the used nic's are:
SBS-server 2 x Broadcom NetXtreme Gigabit, teaming with BASP Virtual Adapter
(perfectly working since 08/2006), (Fujitsu-Siemens Server,Primergy RX300 S2,
rack)
TS 2 x Intel Pro/1000 MT Dual Port Network, teaming with BASP Virtual
Adabpter (perfectly working since 08/2006) (Fujitsu-Siemens Server,Primergy
RX200 S2, rack)
DWH Intel 82566DM-2 Gigabit (Fujitsu-Siemens Server, Primergy Econel 100 S2,
floorstand), new, working for 2 weeks

 

Andy,

Totally off the wall and just humor me. Plug the DHW and the TS into 2
different ports on your switch and test again. I had a similar issue a while
back and it turned out to be the switch communication between those 2 ports.
Otherwise the switch was working fine.

--
Claus

 

Thank you all for the help. I solved the problem.
Nothing with errors in SBS, TS or W2k, or switch.

I found some parameters (with a network-tool) in the lan-card, regarding the
"TCP checksum offload". The parameters were set in a way, that the
network-card did the calculation of the checksums. In the moment I disabled
this parameters and the w2k3-system had to do this calculation, all went ok.

Thank's all for the help.

 

Great

It is not without reason the the Diva calls them evil:
http://msmvps.com/blogs/bradley/archive/2007/01/04/the-following-network-cards-are-evil.aspx

Thomas.