Re: Add remote client PC...remotely! (problem)

From: Dan Freer (spam_at_nospam.com)
Date: 01/27/05 

Date: Thu, 27 Jan 2005 16:43:35 -0000

Thanks Colin, this looks useful, i'll try this and re-post results back
here.

"Colin T" <ColinT@discussions.microsoft.com> wrote in message
news:2D65D606-4BE7-4118-9018-D2C7E2780CF7@microsoft.com...
> http://www.smallbizserver.net/Default.aspx?tabid=167
>
> "Dan Freer" wrote:
>
>> We have a SBS Standard installation (single NIC), all seems to work well
>> with LAN connected client computers etc.
>>
>> However, we are soon to take delivery of a new PC for use as a REMOTE
>> CLIENT, so I thought I'd get ready for this day by trying to connect my
>> own
>> PC at home to the office network.
>>
>> My home PC runs XP Pro, and is setup as a WORKGROUP client, so I thought
>> I
>> would connect to the office VPN (this seems to work fine after much
>> struggle), then change the computer setup by joining it to the domain (My
>> Computer/Properties/Computer Name/CHANGE etc.)
>>
>> The problem is when I get to the bit where it asks for the domain name,
>> is
>> reports the following error:
>>
>> "A domain controller for the domain ourcompanyname could not be
>> contacted"
>>
>> Not sure if this is a helps, but if I do "\\sbs2003" in Start/Run on my
>> home
>> PC when connected to the VPN, it shows all the SHARES on SBS2003, and I
>> can
>> access them fine !
>>
>> Also I can PING all addresses on the office network.
>>
>> The router is at address 192.168.1.254
>>
>> I am not even sure if it is possible to configure the remote client in
>> this
>> way (ie. remotely), maybe I have to set it up in the office then take it
>> away to its remote location?
>>
>> I would very much appreciate any help.
>>
>> IPCONFIGS are shown below for both server and remote client.
>>
>> Kind regards
>> Dan
>>
>>
>>
>>
>> Here is IPCONFIG /ALL for server:
>>
>> Windows IP Configuration
>>
>> Host Name . . . . . . . . . . . . : SBS2003
>> Primary Dns Suffix . . . . . . . : ourcompanyname.local
>> Node Type . . . . . . . . . . . . : Unknown
>> IP Routing Enabled. . . . . . . . : Yes
>> WINS Proxy Enabled. . . . . . . . : Yes
>> DNS Suffix Search List. . . . . . : ourcompanyname.local
>>
>> PPP adapter RAS Server (Dial In) Interface:
>>
>> Connection-specific DNS Suffix . :
>> Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
>> Physical Address. . . . . . . . . : 00-53-45-00-00-00
>> DHCP Enabled. . . . . . . . . . . : No
>> IP Address. . . . . . . . . . . . : 192.168.1.15
>> Subnet Mask . . . . . . . . . . . : 255.255.255.255
>> Default Gateway . . . . . . . . . :
>> NetBIOS over Tcpip. . . . . . . . : Disabled
>>
>> Ethernet adapter Server Local Area Connection:
>>
>> Connection-specific DNS Suffix . :
>> Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
>> Connection
>> Physical Address. . . . . . . . . : 00-11-11-4C-05-1A
>> DHCP Enabled. . . . . . . . . . . : No
>> IP Address. . . . . . . . . . . . : 192.168.1.1
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 192.168.1.254
>> DNS Servers . . . . . . . . . . . : 192.168.1.1
>> Primary WINS Server . . . . . . . : 192.168.1.1
>>
>>
>> Here is IPCONFIG /ALL for remote (when VPN connectected):
>>
>> Windows IP Configuration
>>
>> Host Name . . . . . . . . . . . . : Quaddra
>> Primary Dns Suffix . . . . . . . :
>> Node Type . . . . . . . . . . . . : Unknown
>> IP Routing Enabled. . . . . . . . : Yes
>> WINS Proxy Enabled. . . . . . . . : Yes
>> DNS Suffix Search List. . . . . . : ourcompanyname.local
>>
>> Ethernet adapter Bluetooth Network:
>> Media State . . . . . . . . . . . : Media disconnected
>> Description . . . . . . . . . . . : Bluetooth LAN Access Server
>> Driver
>> Physical Address. . . . . . . . . : 00-07-61-14-19-AD
>>
>> Ethernet adapter Local Area Connection:
>> Connection-specific DNS Suffix . :
>> Description . . . . . . . . . . . : Realtek RTL8139/810x Family
>> Fast
>> Ethernet NIC
>> Physical Address. . . . . . . . . : 00-90-F5-1A-4E-92
>> Dhcp Enabled. . . . . . . . . . . : Yes
>> Autoconfiguration Enabled . . . . : Yes
>> IP Address. . . . . . . . . . . . : 192.168.40.200
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 192.168.40.1
>> DHCP Server . . . . . . . . . . . : 192.168.40.1
>> DNS Servers . . . . . . . . . . . : 192.168.40.1
>> Lease Obtained. . . . . . . . . . : 27 January 2005 07:38:31
>> Lease Expires . . . . . . . . . . : 30 January 2005 07:38:31
>>
>> PPP adapter Connect to Small Business Server:
>>
>> Connection-specific DNS Suffix . : ourcompanyname.local
>> Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
>> Physical Address. . . . . . . . . : 00-53-45-00-00-00
>> Dhcp Enabled. . . . . . . . . . . : No
>> IP Address. . . . . . . . . . . . : 192.168.1.10
>> Subnet Mask . . . . . . . . . . . : 255.255.255.255
>> Default Gateway . . . . . . . . . : 192.168.1.10
>> DNS Servers . . . . . . . . . . . : 192.168.1.1
>> Primary WINS Server . . . . . . . : 192.168.1.1
>>
>>
>>
>>

Relevant Pages

  • Re: Making DB changes as client... crazy??
    ... Database) and the connection drops, ... you and the client drops, the client machine keeps grinding away. ... being a direct remote guest that causes the most risk. ... actually a protection to you and the customer. ...
    (comp.databases.filemaker)
  • Re: probs. with remote desktop via Remote Web Workplace
    ... in order to allow a remote desktop connection to a client ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • RE: RWW not working on some client desktops
    ... computer is in the Remote Desktop Users group. ... Microsoft CSS Online Newsgroup Support ... RWW not working on some client desktops ... >> remote computer's connection request. ...
    (microsoft.public.windows.server.sbs)
  • Re: lsass.exe problem when logging into terminal server.
    ... I assume that your rdp client is not comfigured with a username, ... directly after reboot I can remote desktop into ... > "The client could not establish a connection to the remote ... > 1)Remote connections migh not be enabled at the remote computer ...
    (microsoft.public.win2000.termserv.apps)
  • RE: Add remote client PC...remotely! (problem)
    ... > with LAN connected client computers etc. ... we are soon to take delivery of a new PC for use as a REMOTE ... > Ethernet adapter Server Local Area Connection: ...
    (microsoft.public.windows.server.sbs)
Loading