WIN XP PRO acting as VPN SERVER - Can connect but not use any resources on server

Problem with VPN Server Connection Win XP Pro. I have created a vpn incoming connection on my windows xp pro pc using the supplied wizard. I have created the vpn to allow access to other computers on my lan, I have setup a range of IP address for the VPN, same network ID as my current network. Everything appears to go just fine. At my win xp pro client side, I created a new connection for a VPN connection. One more note, I am using Verizon DSL at both ends, I have utiliaed dyndns.org to create a concept of a static IP address to the server. In addition I have port forwarded 1723 to the win xp pro pc acting as a vpn server. When I perform the dialing at the clinet side I get an error indicating that the connectin was made but there was an errror in the ipx/spx protocol.  I check the IP address of the VPN and see one for the client and one for the server. I am able to ping the server IP address from the client without any problem. However I am using a client server application that will allow me to input the ip address of the vpn server to make the connection. When I do this get the error unable to connect to ip address 192.168.1.251 (server address) port 5052. I have disable the firewall at the other end and still get the error. We do not have domains and we are using simple workgroup peer to peer networking. In addition when the VPN client is connected to the server I can't see any of the resources on the server side.
What is missing here can anyone help me? This is a real serious problem for one of my clients.
FredJRobinsonAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

SysExpertCommented:
1) You should be using TCPIP, not IPX/SPx as your network protocol.

Fix that and the issue should go away.

I hope this helps !
0
FredJRobinsonAuthor Commented:
At the host side we had tcp/ip, file &printer sharing, client for microsoft networks, QOS packet scheduler as services for the vpn connection. It was the client that got the error. I am assuming that it must have ipx/spx as an item that it is using. If both tcp/ip & ipx/spx are defined as items that the client uses will it cause a problem accessing files at the host?
0
SysExpertCommented:
Client should not need ipx at all unless acessing a very old Novell server, so it should be disabled.

That may resolve the issue since that is the error you are getting.

QOS on the sever can also be turned off.

I hope this helps !
0
FredJRobinsonAuthor Commented:
Ok, will try your suggestions and post here the results.
0
FredJRobinsonAuthor Commented:
It ends up that the verizon dsl modem / router on the server side was defective. Replaced their router with a vpn router and standard dsl modem and everything started to work properly.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Broadband

From novice to tech pro — start learning today.