How to network home and office without terminal services??

Hi, I would like to network my home pc to my office pc
(running server 2k3) via a vpn (probably a linksys router -
hardware vpn). I just wanna have access to a specific
drive at the office so that I may work on some documents,
I don't wanna run remote desktop or terminal services, how
can I just log into the office network as if I was just
part of the local network?

Any help would be appreciated!

Sarven


Sarven

Here's what i would do, assuming your machine at home is not on a domain but
is just a stand-alone machine.

You can not log into a Domain that the machine is not a member of. So...

1. Take your "home" machine to work.
2. Join it to the Domain
3. Take it back home
4. During normal use log in locally (third line of login is the machinename)
5. When you want to use it with your network at work, log off the machine
6. Hit Ctrl-Alt-Del again and check the box at the login screen that says
"log on using dialup connection".
7. Choose the VPN Dialup from the choices.
8. The machine will activate the Dialup and login to the Domain over VPN and
go to the Desktop similar to how it would if you had a Domain at home.

Note: You *will* be treated as a different user, you *will* have a different
user profile. The fact that it may be an identical username and password is
meaningless, one account exists on the Domain and the other exists on your
Local machine, so it is not going to treat the two as the same user.

You can skip all this and just use the machine normally as you are and start
the VPN Dialup and try to acess the files but you will be prompted for
credentials. The prompt will only have two lines so you will have to prefix
the username with the remote Domain name to be accepted. Like this:

User: domain\username
Password: ********

Do *not* expect name resolution and network "browsing abilities". Browsing
abilities require Domain Membership or at least a matching Workgroup name.
Name resolution requires a WINS Server from the target Domain being entered
into the VPN Dialup connectiod's TCP/IP properties.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Sarven" <(E-Mail Removed)> wrote in message
news:31aa01c3fcec$910dd4b0$(E-Mail Removed)...
> Hi, I would like to network my home pc to my office pc
> (running server 2k3) via a vpn (probably a linksys router -
> hardware vpn). I just wanna have access to a specific
> drive at the office so that I may work on some documents,
> I don't wanna run remote desktop or terminal services, how
> can I just log into the office network as if I was just
> part of the local network?
>
> Any help would be appreciated!
>
> Sarven

"Phillip Windell" <@.> wrote in message news:<OpDh7kU$(E-Mail Removed)>...
> Here's what i would do, assuming your machine at home is not on a domain but
> is just a stand-alone machine.
>
> You can not log into a Domain that the machine is not a member of. So...
>
> 1. Take your "home" machine to work.
> 2. Join it to the Domain
> 3. Take it back home
> 4. During normal use log in locally (third line of login is the machinename)
> 5. When you want to use it with your network at work, log off the machine
> 6. Hit Ctrl-Alt-Del again and check the box at the login screen that says
> "log on using dialup connection".
> 7. Choose the VPN Dialup from the choices.
> 8. The machine will activate the Dialup and login to the Domain over VPN and
> go to the Desktop similar to how it would if you had a Domain at home.
>
> Note: You *will* be treated as a different user, you *will* have a different
> user profile. The fact that it may be an identical username and password is
> meaningless, one account exists on the Domain and the other exists on your
> Local machine, so it is not going to treat the two as the same user.
>
> You can skip all this and just use the machine normally as you are and start
> the VPN Dialup and try to acess the files but you will be prompted for
> credentials. The prompt will only have two lines so you will have to prefix
> the username with the remote Domain name to be accepted. Like this:
>
> User: domain\username
> Password: ********
>
> Do *not* expect name resolution and network "browsing abilities". Browsing
> abilities require Domain Membership or at least a matching Workgroup name.
> Name resolution requires a WINS Server from the target Domain being entered
> into the VPN Dialup connectiod's TCP/IP properties.
>
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
> "Sarven" <(E-Mail Removed)> wrote in message
> news:31aa01c3fcec$910dd4b0$(E-Mail Removed)...
> > Hi, I would like to network my home pc to my office pc
> > (running server 2k3) via a vpn (probably a linksys router -
> > hardware vpn). I just wanna have access to a specific
> > drive at the office so that I may work on some documents,
> > I don't wanna run remote desktop or terminal services, how
> > can I just log into the office network as if I was just
> > part of the local network?
> >
> > Any help would be appreciated!
> >
> > Sarven


I have everything setup correctly and am able to vpn no problem. but i
still cant browse the other computers on my remote lan. DNS and WINS
servers are up and running and the address for then is entered in my
vpn connetions tcp/ip properties. so why cant i browse?

As Phillip has already pointed out, you can't browse the remote LAN
unless you are a member of the domain (or somehow get the domain name known
on the client).

A full explanation of why would take half a book. Briefly, your remote
client is not on the LAN, so it can't use LAN broadcasts. So it is not in
the LAN browse list. But it can get a browse list for the LAN if it asks the
right questions. If it is aware of the domain name, it will send a name
server request to WINS for the Netbios name "domainname 1B" , which is the
domain master browser. WINS should reply with the IP address of the DMB. The
client can then get a browse list from the DMB . It should look just like
the browse list which the LAN clients see.

If you are keen, you can monitor the traffic on the link and see exactly
what the client is requesting (and why it fails).

"mai1_host" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> "Phillip Windell" <@.> wrote in message
news:<OpDh7kU$(E-Mail Removed)>...
> > Here's what i would do, assuming your machine at home is not on a domain
but
> > is just a stand-alone machine.
> >
> > You can not log into a Domain that the machine is not a member of. So...
> >
> > 1. Take your "home" machine to work.
> > 2. Join it to the Domain
> > 3. Take it back home
> > 4. During normal use log in locally (third line of login is the
machinename)
> > 5. When you want to use it with your network at work, log off the
machine
> > 6. Hit Ctrl-Alt-Del again and check the box at the login screen that
says
> > "log on using dialup connection".
> > 7. Choose the VPN Dialup from the choices.
> > 8. The machine will activate the Dialup and login to the Domain over VPN
and
> > go to the Desktop similar to how it would if you had a Domain at home.
> >
> > Note: You *will* be treated as a different user, you *will* have a
different
> > user profile. The fact that it may be an identical username and password
is
> > meaningless, one account exists on the Domain and the other exists on
your
> > Local machine, so it is not going to treat the two as the same user.
> >
> > You can skip all this and just use the machine normally as you are and
start
> > the VPN Dialup and try to acess the files but you will be prompted for
> > credentials. The prompt will only have two lines so you will have to
prefix
> > the username with the remote Domain name to be accepted. Like this:
> >
> > User: domain\username
> > Password: ********
> >
> > Do *not* expect name resolution and network "browsing abilities".
Browsing
> > abilities require Domain Membership or at least a matching Workgroup
name.
> > Name resolution requires a WINS Server from the target Domain being
entered
> > into the VPN Dialup connectiod's TCP/IP properties.
> >
> >
> > --
> >
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> >
> >
> > "Sarven" <(E-Mail Removed)> wrote in message
> > news:31aa01c3fcec$910dd4b0$(E-Mail Removed)...
> > > Hi, I would like to network my home pc to my office pc
> > > (running server 2k3) via a vpn (probably a linksys router -
> > > hardware vpn). I just wanna have access to a specific
> > > drive at the office so that I may work on some documents,
> > > I don't wanna run remote desktop or terminal services, how
> > > can I just log into the office network as if I was just
> > > part of the local network?
> > >
> > > Any help would be appreciated!
> > >
> > > Sarven
>
>
> I have everything setup correctly and am able to vpn no problem. but i
> still cant browse the other computers on my remote lan. DNS and WINS
> servers are up and running and the address for then is entered in my
> vpn connetions tcp/ip properties. so why cant i browse?

"Bill Grant" <not.available@online> wrote in message news:<uEm67PZ$(E-Mail Removed)>...
> As Phillip has already pointed out, you can't browse the remote LAN
> unless you are a member of the domain (or somehow get the domain name known
> on the client).
>
> A full explanation of why would take half a book. Briefly, your remote
> client is not on the LAN, so it can't use LAN broadcasts. So it is not in
> the LAN browse list. But it can get a browse list for the LAN if it asks the
> right questions. If it is aware of the domain name, it will send a name
> server request to WINS for the Netbios name "domainname 1B" , which is the
> domain master browser. WINS should reply with the IP address of the DMB. The
> client can then get a browse list from the DMB . It should look just like
> the browse list which the LAN clients see.
>
> If you are keen, you can monitor the traffic on the link and see exactly
> what the client is requesting (and why it fails).
>
> "mai1_host" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) om...
> > "Phillip Windell" <@.> wrote in message
> news:<OpDh7kU$(E-Mail Removed)>...
> > > Here's what i would do, assuming your machine at home is not on a domain
> but
> > > is just a stand-alone machine.
> > >
> > > You can not log into a Domain that the machine is not a member of. So...
> > >
> > > 1. Take your "home" machine to work.
> > > 2. Join it to the Domain
> > > 3. Take it back home
> > > 4. During normal use log in locally (third line of login is the
> machinename)
> > > 5. When you want to use it with your network at work, log off the
> machine
> > > 6. Hit Ctrl-Alt-Del again and check the box at the login screen that
> says
> > > "log on using dialup connection".
> > > 7. Choose the VPN Dialup from the choices.
> > > 8. The machine will activate the Dialup and login to the Domain over VPN
> and
> > > go to the Desktop similar to how it would if you had a Domain at home.
> > >
> > > Note: You *will* be treated as a different user, you *will* have a
> different
> > > user profile. The fact that it may be an identical username and password
> is
> > > meaningless, one account exists on the Domain and the other exists on
> your
> > > Local machine, so it is not going to treat the two as the same user.
> > >
> > > You can skip all this and just use the machine normally as you are and
> start
> > > the VPN Dialup and try to acess the files but you will be prompted for
> > > credentials. The prompt will only have two lines so you will have to
> prefix
> > > the username with the remote Domain name to be accepted. Like this:
> > >
> > > User: domain\username
> > > Password: ********
> > >
> > > Do *not* expect name resolution and network "browsing abilities".
> Browsing
> > > abilities require Domain Membership or at least a matching Workgroup
> name.
> > > Name resolution requires a WINS Server from the target Domain being
> entered
> > > into the VPN Dialup connectiod's TCP/IP properties.
> > >
> > >
> > > --
> > >
> > > Phillip Windell [MCP, MVP, CCNA]
> > > www.wandtv.com
> > >
> > >
> > > "Sarven" <(E-Mail Removed)> wrote in message
> > > news:31aa01c3fcec$910dd4b0$(E-Mail Removed)...
> > > > Hi, I would like to network my home pc to my office pc
> > > > (running server 2k3) via a vpn (probably a linksys router -
> > > > hardware vpn). I just wanna have access to a specific
> > > > drive at the office so that I may work on some documents,
> > > > I don't wanna run remote desktop or terminal services, how
> > > > can I just log into the office network as if I was just
> > > > part of the local network?
> > > >
> > > > Any help would be appreciated!
> > > >
> > > > Sarven
> >
> >
> > I have everything setup correctly and am able to vpn no problem. but i
> > still cant browse the other computers on my remote lan. DNS and WINS
> > servers are up and running and the address for then is entered in my
> > vpn connetions tcp/ip properties. so why cant i browse?


Here is what i have done so far.
On the server side port 1723 is forwaded from the router to the
server.
The PDC is the vpn,dns,wins server 192.168.1.x. On the client side i
have the address of the PDC entered in the vpn's connection dns and
wins properties
and i connect perfectly well.


I tested the wins by stopping the service on server and i could not
do a \\computername\sharename after it was stopped.

I tested DNS by stopping it on the server and i could not browse so i
know that it is working so why cant i get the browse list from server.
Im conected and my workgroup is ABAB. I can \\coputername\Sharename
anywhere on remote network, I can resolve dns from remote network but
when i view workgroup or try to browse my network Im the only computer
listed. you mentioned monitoring traffic to see where it fails any
ideas on who to accomplish that.
Windows IP Configuration

Host Name . . . . . . . . . . . . : Mycomp
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NETGEAR FA311 Fast
Ethernet Adapter
Physical Address. . . . . . . . . : 00-02-E3-09-8F-2D
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1

PPP adapter ABAB:

Connection-specific DNS Suffix . : ABAB.local
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.33
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 192.168.1.33
DNS Servers . . . . . . . . . . . : 192.168.1.3
192.168.1.3
Primary WINS Server . . . . . . . : 192.168.1.3
Secondary WINS Server . . . . . . : 192.168.1.3

The browser service does not use DNS. It relies on broadcasts. If your
isolated machine is in a workgroup, it will not be able to browse. It is in
a browse group of one! Your only chance is for it to find the Domain Master
Browser (using WINS) and get the domain browse list (which will not include
the remote client).

"mai1_host" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) m...
> "Bill Grant" <not.available@online> wrote in message
news:<uEm67PZ$(E-Mail Removed)>...
> > As Phillip has already pointed out, you can't browse the remote LAN
> > unless you are a member of the domain (or somehow get the domain name
known
> > on the client).
> >
> > A full explanation of why would take half a book. Briefly, your
remote
> > client is not on the LAN, so it can't use LAN broadcasts. So it is not
in
> > the LAN browse list. But it can get a browse list for the LAN if it asks
the
> > right questions. If it is aware of the domain name, it will send a name
> > server request to WINS for the Netbios name "domainname 1B" , which is
the
> > domain master browser. WINS should reply with the IP address of the DMB.
The
> > client can then get a browse list from the DMB . It should look just
like
> > the browse list which the LAN clients see.
> >
> > If you are keen, you can monitor the traffic on the link and see
exactly
> > what the client is requesting (and why it fails).
> >
> > "mai1_host" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed) om...
> > > "Phillip Windell" <@.> wrote in message
> > news:<OpDh7kU$(E-Mail Removed)>...
> > > > Here's what i would do, assuming your machine at home is not on a
domain
> > but
> > > > is just a stand-alone machine.
> > > >
> > > > You can not log into a Domain that the machine is not a member of.
So...
> > > >
> > > > 1. Take your "home" machine to work.
> > > > 2. Join it to the Domain
> > > > 3. Take it back home
> > > > 4. During normal use log in locally (third line of login is the
> > machinename)
> > > > 5. When you want to use it with your network at work, log off the
> > machine
> > > > 6. Hit Ctrl-Alt-Del again and check the box at the login screen that
> > says
> > > > "log on using dialup connection".
> > > > 7. Choose the VPN Dialup from the choices.
> > > > 8. The machine will activate the Dialup and login to the Domain over
VPN
> > and
> > > > go to the Desktop similar to how it would if you had a Domain at
home.
> > > >
> > > > Note: You *will* be treated as a different user, you *will* have a
> > different
> > > > user profile. The fact that it may be an identical username and
password
> > is
> > > > meaningless, one account exists on the Domain and the other exists
on
> > your
> > > > Local machine, so it is not going to treat the two as the same user.
> > > >
> > > > You can skip all this and just use the machine normally as you are
and
> > start
> > > > the VPN Dialup and try to acess the files but you will be prompted
for
> > > > credentials. The prompt will only have two lines so you will have to
> > prefix
> > > > the username with the remote Domain name to be accepted. Like this:
> > > >
> > > > User: domain\username
> > > > Password: ********
> > > >
> > > > Do *not* expect name resolution and network "browsing abilities".
> > Browsing
> > > > abilities require Domain Membership or at least a matching Workgroup
> > name.
> > > > Name resolution requires a WINS Server from the target Domain being
> > entered
> > > > into the VPN Dialup connectiod's TCP/IP properties.
> > > >
> > > >
> > > > --
> > > >
> > > > Phillip Windell [MCP, MVP, CCNA]
> > > > www.wandtv.com
> > > >
> > > >
> > > > "Sarven" <(E-Mail Removed)> wrote in message
> > > > news:31aa01c3fcec$910dd4b0$(E-Mail Removed)...
> > > > > Hi, I would like to network my home pc to my office pc
> > > > > (running server 2k3) via a vpn (probably a linksys router -
> > > > > hardware vpn). I just wanna have access to a specific
> > > > > drive at the office so that I may work on some documents,
> > > > > I don't wanna run remote desktop or terminal services, how
> > > > > can I just log into the office network as if I was just
> > > > > part of the local network?
> > > > >
> > > > > Any help would be appreciated!
> > > > >
> > > > > Sarven
> > >
> > >
> > > I have everything setup correctly and am able to vpn no problem. but i
> > > still cant browse the other computers on my remote lan. DNS and WINS
> > > servers are up and running and the address for then is entered in my
> > > vpn connetions tcp/ip properties. so why cant i browse?
>
>
> Here is what i have done so far.
> On the server side port 1723 is forwaded from the router to the
> server.
> The PDC is the vpn,dns,wins server 192.168.1.x. On the client side i
> have the address of the PDC entered in the vpn's connection dns and
> wins properties
> and i connect perfectly well.
>
>
> I tested the wins by stopping the service on server and i could not
> do a \\computername\sharename after it was stopped.
>
> I tested DNS by stopping it on the server and i could not browse so i
> know that it is working so why cant i get the browse list from server.
> Im conected and my workgroup is ABAB. I can \\coputername\Sharename
> anywhere on remote network, I can resolve dns from remote network but
> when i view workgroup or try to browse my network Im the only computer
> listed. you mentioned monitoring traffic to see where it fails any
> ideas on who to accomplish that.
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : Mycomp
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : NETGEAR FA311 Fast
> Ethernet Adapter
> Physical Address. . . . . . . . . : 00-02-E3-09-8F-2D
> Dhcp Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.4
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 192.168.1.1
>
> PPP adapter ABAB:
>
> Connection-specific DNS Suffix . : ABAB.local
> Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
> Physical Address. . . . . . . . . : 00-53-45-00-00-00
> Dhcp Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.33
> Subnet Mask . . . . . . . . . . . : 255.255.255.255
> Default Gateway . . . . . . . . . : 192.168.1.33
> DNS Servers . . . . . . . . . . . : 192.168.1.3
> 192.168.1.3
> Primary WINS Server . . . . . . . : 192.168.1.3
> Secondary WINS Server . . . . . . : 192.168.1.3

Sorry Bill, Maybe your misunderstanding me. I have a Wins server. My
VPN clients connection is pointed to it. I have also joined this
machine to the Domain. and it still does not produce a list of
computers in My Network Places. I have gone as far as logging in to
the domain from my clients logon by selecting connect using dialup
networking (VPN Connection). that means the client machine is
authenticated to the domain. still no other computers are in my
network places.

I can only repeat what I said before. The only way to be sure what is
happening is to monitor the traffic crossing the link. Then you will see
exactly what the client sends ans what reply it receives.

"mai1_host" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> Sorry Bill, Maybe your misunderstanding me. I have a Wins server. My
> VPN clients connection is pointed to it. I have also joined this
> machine to the Domain. and it still does not produce a list of
> computers in My Network Places. I have gone as far as logging in to
> the domain from my clients logon by selecting connect using dialup
> networking (VPN Connection). that means the client machine is
> authenticated to the domain. still no other computers are in my
> network places.

I Thank you for taking time to respond to my posts. But i have no idea
as how to monitor traffic between the link is theier a program you can
recommend. or give me an idea of how to do what you are suggesting.

Network Monitor is included with the server software, or you can use
third party software.

With NetMon, you install it on the server (from Control Panel |
Add/Remove Windows Components) . When you start up, it will normally ask
what interface you want to monitor. Select the VPN interface. Then start a
capture. It will record all traffic until you stop it. You can then display
the captured data, and save it if required.

"mai1_host" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> I Thank you for taking time to respond to my posts. But i have no idea
> as how to monitor traffic between the link is theier a program you can
> recommend. or give me an idea of how to do what you are suggesting.