Re: SBS 2003 with additional terminalserver and additional dwh-ser

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

"Cris Hanna [SBS-MVP]" wrote:

Lots of folks run additional servers in addition to SBS without any difficulty

If you get on the SBS server, can you ping the TS server by IP and does it return the proper name, if you ping by name, does it return the proper IP?
What about the DWH server, does it respond properly by IP and name

Now repeat from the TS to the DWH server, ping by IP and by Name...do you get the proper responses?

I would also disable the NIC teaming stuff on the TS and see if things improve

--
Cris Hanna [SBS - MVP]
-----------------------------------------------------------
MVPs Do Not Work for Microsoft
Please do not contact me directly regarding issues
"Andy" <asabukoschek@xxxxxxxx> wrote in message news:DF4EE01B-C7F9-4225-8699-9381D76541BE@xxxxxxxxxxxxxxxx
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 E2180@xxx 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
.

Relevant Pages

  • Re: SBS 2003 with additional terminalserver and additional dwh-ser
    ... Have not worked with TS in a SBS environment except once and that was with 2000. ... So how new is the DWH server and has the problem always existed?? ... > When I ping the ts from sbs by name it responds with correct ip, ...
    (microsoft.public.windows.server.sbs)
  • RE: cannot connect computer
    ... if I type in the url of the server i get through ok. ... client computer to SBS domain. ... | I am unable to ping the sbs server by ip or name. ...
    (microsoft.public.windows.server.sbs)
  • Re: Connecting to Exchange...
    ... That means that SBS has a static *private* IP on your LAN. ... Not being able to ping "the server" is probably not a sign of a problem...and is also technically inaccurate. ... I understand the desire to keep your server minimalist and only run exchange, but DNS and DHCP should be considered "essential" SBS components. ...
    (microsoft.public.windows.server.sbs)
  • Re: Connecting to Exchange...
    ... It is held by SBS. ... There is no router in between the ISP's connection and the SBS server. ... So in essence, the WAN port will not ping, but it does get out on the internet, and OWA will work through it. ... That would be a very odd configuration considering what 'appears' to be the rest of your network layout. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 with additional terminalserver and additional dwh-ser
    ... back and it turned out to be the switch communication between those 2 ports. ... So how new is the DWH server and has the problem always existed?? ... Cris Hanna [SBS - MVP] ...
    (microsoft.public.windows.server.sbs)
Loading