Re: Unable to connect new vista terminal to SBS 2003 R2
- From: "Claus" <cjobes@xxxxxxxxxxxxx>
- Date: Fri, 10 Aug 2007 17:34:48 -0400
Post a new IP config from the server LAN and that workstation. Also, did you
check that there is only ONE NIC active on the workstation? If it does have
a build-in wireless or any VPN connector installed, you need to disable
those. Only the LAN NIC should be active when you try to join it into the
domain.
--
Claus
"kwhittle" <kwhittle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6D2ED4CC-3E96-4420-B8BA-6B5B3B886995@xxxxxxxxxxxxxxxx
Hi Claus
Ok, have changed the LAN properties as instucted, but the workstation
still
won't connect.
Any other ideas?
Keith
"Claus" wrote:
You need to make the change on you LAN card. The LAN card is currently
pointing to 2.1.as the WINS instead of 2.2.
Go to the LAN properties, select TCP/IP, select properties, click on the
advanced tab, click on the WINS tab and change the IP to 2.2.
--
Claus
"kwhittle" <kwhittle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B40199BB-4F4B-49B7-B880-B5E5ABA96F93@xxxxxxxxxxxxxxxx
Hi Claus,
Sorry to be a dunce and be a bit over cautious but being a newbie I'm
not
wanting to change the wrong thing!
Can you let me know exactly what it is I need to do. I've looked at
WINS
in
advanced management and can't obviously see what you are referring to,
or
do
I need to go in to properties of the lan network connection?
Thanks again for all your continued help!
Keith
"Claus" wrote:
Your WINS server on the SBS LAN is pointing to the wrong IP. It should
be
pointing to 2.2. Change this and try if that fixes your issue.
--
Claus
"kwhittle" <kwhittle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7840200B-7B37-41C3-91A3-54DB7CC88088@xxxxxxxxxxxxxxxx
Sorry Claus that last copy and paste didn't include everything.
Below are both ipconfig /all in full
SBS - Windows IP Configuration
Host Name . . . . . . . . . . . . : <servername>
Primary Dns Suffix . . . . . . . : <domainname>
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : <domainname>
Ethernet adapter Server Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce Networking
Controller
Physical Address. . . . . . . . . : 00-13-8F-CC-07-D3
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.2
Primary WINS Server . . . . . . . : 192.168.2.1
Mental Health - Windows IP Configuration
Host Name . . . . . . . . . . . . : Machine3
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : <domainname>
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connection
Physical Address. . . . . . . . . : 00-13-20-AF-5B-FF
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : <domainname>
Description . . . . . . . . . . . : Broadcom 802.11g Network
Adapter
Physical Address. . . . . . . . . : 00-11-50-3F-B0-43
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
fe80::e06e:1d4b:5d51:8c20%8(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.2.28(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 09 August 2007 17:32:01
Lease Expires . . . . . . . . . . : 17 August 2007 17:32:00
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.2
DHCPv6 IAID . . . . . . . . . . . : 134222160
DNS Servers . . . . . . . . . . . : 192.168.2.2
Primary WINS Server . . . . . . . : 192.168.2.2
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Local Area Connection* 6:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{1131B7A8-4FFD-4667-BDCD-0AD4AC7F9
F2D}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 7:
Connection-specific DNS Suffix . : <domainname>
Description . . . . . . . . . . . : isatap.<domainname>
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
fe80::5efe:192.168.2.28%11(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.2.2
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter Local Area Connection* 9:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling
Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . :
2001:0:4136:e38c:342a:33c7:3f57:fde3(Pref
erred)
Link-local IPv6 Address . . . . . :
fe80::342a:33c7:3f57:fde3%12(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled
"kwhittle" wrote:
Hi Claus
Yes i have out that patch on, to no avail I'm afraid to say.
Here are the ipconfig /all resposes you requested
SBS
Windows IP Configuration
Host Name . . . . . . . . . . . . : <servername>
Primary Dns Suffix . . . . . . . : <domainname>
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : <domainname>
Ethernet adapter Server Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce Networking
Controller
Physical Address. . . . . . . . . : 00-13-8F-CC-07-D3
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.2
Primary WINS Server . . . . . . . : 192.168.2.1
Vista Workstation
Windows IP Configuration
Host Name . . . . . . . . . . . . : <servername>
Primary Dns Suffix . . . . . . . : <domainname>
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : <domainname>
Ethernet adapter Server Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce Networking
Controller
Physical Address. . . . . . . . . : 00-13-8F-CC-07-D3
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.2
Primary WINS Server . . . . . . . : 192.168.2.1
Hope this helps
Keith
"Claus" wrote:
did you put the patch on that box?
http://support.microsoft.com/kb/926505
Post an ipconfig /all from your SBS and from that one Vista box.
--
Claus
"kwhittle" <kwhittle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F36F4F77-745A-4C47-B401-400D2EA1F919@xxxxxxxxxxxxxxxx
In follow up to my last post, If i manually try to connect to
the
domain,
I
get the following error message...
"Note: This information is intended for a network
administrator.
If
you
are
not your network's administrator, notify the administrator that
you
received
this information, which has been recorded in the file
C:\Windows\debug\dcdiag.txt.
The following error occurred when DNS was queried for the
service
location
(SRV) resource record used to locate an Active Directory Domain
Controller
for domain domainname.local:
The error was: "DNS server failure."
(error code 0x0000232A RCODE_SERVER_FAILURE)
The query was for the SRV record for
_ldap._tcp.dc._msdcs.domainname.local
Common causes of this error include the following:
- The DNS servers used by this computer contain incorrect root
hints.
This
computer is configured to use DNS servers with the following IP
addresses:
192.168.2.2
- One or more of the following zones contains incorrect
delegation:
domainname.local
local
. (the root zone)
"kwhittle" wrote:
Thanks for the suggestions, but still no luck. I have 11 other
Vista
Enterprise terminals running off the server and I had no
problem
with
setting
those up.
Once again I am open to suggestions, I'm wondering if maybe it
is
a
Reverse
DNS problem, as the message states 'error occured when
configuring
network
settings'? If it is a DNS issue, I am not very good on this
(sorry
still
a
newbie to all this) So would welcome any/all help and a walk
through.
Hope someone can help
Keith
"Steve" wrote:
Agree with Claus. Best practice with SBS is to use the
wizards.
"Claus" <cjobes@xxxxxxxxxxxxx> wrote in message
news:%23SKGUGf2HHA.4712@xxxxxxxxxxxxxxxxxxxxxxx
I'm not sure about this advice. Most people in here will
not
agree.
SBS
works best if you use the tools that are provided with it.
Have a look at this it might solve your problem....
http://support.microsoft.com/kb/926505
Note that there are patches for the server AND the Vista
workstation.
--
Claus
"Chris Tortorich" <chris@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
wrote
in
.
- Follow-Ups:
- Re: Unable to connect new vista terminal to SBS 2003 R2
- From: kwhittle
- Re: Unable to connect new vista terminal to SBS 2003 R2
- References:
- Re: Unable to connect new vista terminal to SBS 2003 R2
- From: Chris Tortorich
- Re: Unable to connect new vista terminal to SBS 2003 R2
- From: Claus
- Re: Unable to connect new vista terminal to SBS 2003 R2
- From: Steve
- Re: Unable to connect new vista terminal to SBS 2003 R2
- From: kwhittle
- Re: Unable to connect new vista terminal to SBS 2003 R2
- From: Claus
- Re: Unable to connect new vista terminal to SBS 2003 R2
- From: kwhittle
- Re: Unable to connect new vista terminal to SBS 2003 R2
- From: kwhittle
- Re: Unable to connect new vista terminal to SBS 2003 R2
- From: Claus
- Re: Unable to connect new vista terminal to SBS 2003 R2
- From: kwhittle
- Re: Unable to connect new vista terminal to SBS 2003 R2
- From: Claus
- Re: Unable to connect new vista terminal to SBS 2003 R2
- From: kwhittle
- Re: Unable to connect new vista terminal to SBS 2003 R2
- Prev by Date: Re: Shared network printer conflict problem?
- Next by Date: Re: Blackberry Enterprise Server Express and SBS Premium
- Previous by thread: Re: Unable to connect new vista terminal to SBS 2003 R2
- Next by thread: Re: Unable to connect new vista terminal to SBS 2003 R2
- Index(es):
Relevant Pages
|
Loading