VPN connects but is unusable?!

Windows 2003 Small Business Server with XP Pro client.


I can connect to our VPN, it verifies the username and password and then
logs on to the network. All seems well and good until the next message
appears saying the roaming profile could not be located.

If I try and log on when connected directly to the LAN, all works fine as it
should. Yet when connecting using VPN I get this error.

Once the VPN is connected, it appears to be totally useless, I can't access
shared folders on the server, can't ping any PCs or anything.

The server's IP address on the LAN is 192.168.0.2. (Subnet 255.255.255.0)
LAN IP addresses are set manually and the others are set by the router
(129.168.0.254). When connected via VPN, the client sees the following:


DHCP Enabled: NO
IP Address: 192.168.0.4
Subnet MaskL 255.255.255.255
Default Gateway: 192.168.0.4
Default Gateway: 192.168.0.2
Primary WINS Server: 192.168.0.2


Any help or advice would be very much appreciated!

if you can ping the remote computer by IP but name, you may have name resolution issue.
if you can't ping remote computer IP, make sure IP routing is enabled.

these pages may help,

VPN Name Resolution
VPN as Router
VPN Routing Issues

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Richard Kimberley" <(E-Mail Removed)> wrote in message news:432e95bd$0$3585$(E-Mail Removed). ..
Windows 2003 Small Business Server with XP Pro client.


I can connect to our VPN, it verifies the username and password and then
logs on to the network. All seems well and good until the next message
appears saying the roaming profile could not be located.

If I try and log on when connected directly to the LAN, all works fine as it
should. Yet when connecting using VPN I get this error.

Once the VPN is connected, it appears to be totally useless, I can't access
shared folders on the server, can't ping any PCs or anything.

The server's IP address on the LAN is 192.168.0.2. (Subnet 255.255.255.0)
LAN IP addresses are set manually and the others are set by the router
(129.168.0.254). When connected via VPN, the client sees the following:


DHCP Enabled: NO
IP Address: 192.168.0.4
Subnet MaskL 255.255.255.255
Default Gateway: 192.168.0.4
Default Gateway: 192.168.0.2
Primary WINS Server: 192.168.0.2


Any help or advice would be very much appreciated!

Thanks Robert,

I can't seem to be able to ping any LAN machine or the server by name or IP from the remote VPN client....


"Robert L [MS-MVP]" <(E-Mail Removed)> wrote in message news:%23ru$(E-Mail Removed)...
if you can ping the remote computer by IP but name, you may have name resolution issue.
if you can't ping remote computer IP, make sure IP routing is enabled.

these pages may help,

VPN Name Resolution
VPN as Router
VPN Routing Issues

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Richard Kimberley" <(E-Mail Removed)> wrote in message news:432e95bd$0$3585$(E-Mail Removed). ..
Windows 2003 Small Business Server with XP Pro client.


I can connect to our VPN, it verifies the username and password and then
logs on to the network. All seems well and good until the next message
appears saying the roaming profile could not be located.

If I try and log on when connected directly to the LAN, all works fine as it
should. Yet when connecting using VPN I get this error.

Once the VPN is connected, it appears to be totally useless, I can't access
shared folders on the server, can't ping any PCs or anything.

The server's IP address on the LAN is 192.168.0.2. (Subnet 255.255.255.0)
LAN IP addresses are set manually and the others are set by the router
(129.168.0.254). When connected via VPN, the client sees the following:


DHCP Enabled: NO
IP Address: 192.168.0.4
Subnet MaskL 255.255.255.255
Default Gateway: 192.168.0.4
Default Gateway: 192.168.0.2
Primary WINS Server: 192.168.0.2


Any help or advice would be very much appreciated!

Right the problem was the LAN i'm on with the remote VPN client uses the same IP and subnet as the LAN the VPN server is on. Obviouslt two separate LANS but with the same IPs so conflicting? Changed one LAN to a different IP and all is fine.


"Richard Kimberley" <(E-Mail Removed)> wrote in message news:432ec607$0$3615$(E-Mail Removed). ..
Thanks Robert,

I can't seem to be able to ping any LAN machine or the server by name or IP from the remote VPN client....


"Robert L [MS-MVP]" <(E-Mail Removed)> wrote in message news:%23ru$(E-Mail Removed)...
if you can ping the remote computer by IP but name, you may have name resolution issue.
if you can't ping remote computer IP, make sure IP routing is enabled.

these pages may help,

VPN Name Resolution
VPN as Router
VPN Routing Issues

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Richard Kimberley" <(E-Mail Removed)> wrote in message news:432e95bd$0$3585$(E-Mail Removed). ..
Windows 2003 Small Business Server with XP Pro client.


I can connect to our VPN, it verifies the username and password and then
logs on to the network. All seems well and good until the next message
appears saying the roaming profile could not be located.

If I try and log on when connected directly to the LAN, all works fine as it
should. Yet when connecting using VPN I get this error.

Once the VPN is connected, it appears to be totally useless, I can't access
shared folders on the server, can't ping any PCs or anything.

The server's IP address on the LAN is 192.168.0.2. (Subnet 255.255.255.0)
LAN IP addresses are set manually and the others are set by the router
(129.168.0.254). When connected via VPN, the client sees the following:


DHCP Enabled: NO
IP Address: 192.168.0.4
Subnet MaskL 255.255.255.255
Default Gateway: 192.168.0.4
Default Gateway: 192.168.0.2
Primary WINS Server: 192.168.0.2


Any help or advice would be very much appreciated!

Thank you for the reply. Yes, they should work if they are in the different IP range.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Richard Kimberley" <(E-Mail Removed)> wrote in message news:432ed274$0$3575$(E-Mail Removed). ..
Right the problem was the LAN i'm on with the remote VPN client uses the same IP and subnet as the LAN the VPN server is on. Obviouslt two separate LANS but with the same IPs so conflicting? Changed one LAN to a different IP and all is fine.


"Richard Kimberley" <(E-Mail Removed)> wrote in message news:432ec607$0$3615$(E-Mail Removed). ..
Thanks Robert,

I can't seem to be able to ping any LAN machine or the server by name or IP from the remote VPN client....


"Robert L [MS-MVP]" <(E-Mail Removed)> wrote in message news:%23ru$(E-Mail Removed)...
if you can ping the remote computer by IP but name, you may have name resolution issue.
if you can't ping remote computer IP, make sure IP routing is enabled.

these pages may help,

VPN Name Resolution
VPN as Router
VPN Routing Issues

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Richard Kimberley" <(E-Mail Removed)> wrote in message news:432e95bd$0$3585$(E-Mail Removed). ..
Windows 2003 Small Business Server with XP Pro client.


I can connect to our VPN, it verifies the username and password and then
logs on to the network. All seems well and good until the next message
appears saying the roaming profile could not be located.

If I try and log on when connected directly to the LAN, all works fine as it
should. Yet when connecting using VPN I get this error.

Once the VPN is connected, it appears to be totally useless, I can't access
shared folders on the server, can't ping any PCs or anything.

The server's IP address on the LAN is 192.168.0.2. (Subnet 255.255.255.0)
LAN IP addresses are set manually and the others are set by the router
(129.168.0.254). When connected via VPN, the client sees the following:


DHCP Enabled: NO
IP Address: 192.168.0.4
Subnet MaskL 255.255.255.255
Default Gateway: 192.168.0.4
Default Gateway: 192.168.0.2
Primary WINS Server: 192.168.0.2


Any help or advice would be very much appreciated!