• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1052
  • Last Modified:

Port 10000 problem

Hi all.

I'm using the Cisco VPN client.  When I VPN into the network, I need to connect to an application that is running on port 10000 on a host.

I can browse the host's drives, ping it, etc.  I can do everything fine except connect to the application (it's MAS200), which is running on port 10000.  The host and application is up and running as users in the LAN are able to connect.

The firewall is a Cisco PIX 501.  Is there anything special I have to do to disable some kind of port conflict on port 10000 between the PIX and the VPN client?
0
surbit
Asked:
surbit
  • 4
  • 3
  • 2
  • +1
2 Solutions
 
surbitAuthor Commented:
Oh, one more interesting thing.  I can telnet into the host by the IP address on port 10000.  But when I try to telnet into the host via the computer name, it doesn't work.  Yet I can ping the host by the computer name.

So if I telnet 192.168.1.5 10000, it works.

I can ping host_a and it resolves to 192.168.1.5.

I cannot do this:  telnet host_a 10000.  I do have a WINS server enable for the VPN client.



0
 
surbitAuthor Commented:
No, the above comment is incorrect.

When I ping host_a, it resolves to 192.168.1.10, which is the wrong host.  In fact, whatever I ping, it resolves to the same 192.168.1.10 address.  I can even ping a non-existent host such as adfasfasdfasfsafas and it will resolve to 192.168.1.10.  I think this is the problem.  Any solution?  Thanks.
0
 
FrabbleCommented:
I guess you're also using DNS to resolve names.
Is there a host entry for host_a in your default DNS domain? Given that non existent hosts resolve, I suspect that there is a wildcard address entry (*) pointing to 192.168.1.10 and presenting you with this problem.
0
Improved Protection from Phishing Attacks

WatchGuard DNSWatch reduces malware infections by detecting and blocking malicious DNS requests, improving your ability to protect employees from phishing attacks. Learn more about our newest service included in Total Security Suite today!

 
surbitAuthor Commented:
But the LAN users are using the same DNS server and they can resolve all the names properely.
0
 
guniteCommented:
Just permit UDP port 62515 from any host.
This traffic/ports will never be seen with a packet sniffer because this is local to the PC, communication to loopback address (stuff that occur between the VPN softwares different parts)
0
 
ngravattCommented:
flush your dns.  

open a command prompt, type ipconfig /flushdns

your VPN client uses port 10000, to make connections to the VPN concentrator.
0
 
guniteCommented:
Actually there are a wide range of ports that are used internally when the VPN client initializes. I had to enable the setting that allows UDP port  62515 to receive traffic from any host to get my VPN working through my XP Firewall. Without that the client will die without even trying to get out of the machine.
0
 
ngravattCommented:
yeah, with SP2 for XP, you can add a entries to the windows firewall that will enable the cisco VPN clinets to work.  Here are the only ports that we added.

TCP Port 10000
UDP 4500
UDP 62515

this has worked on many computers.
0
 
surbitAuthor Commented:
There is no Windows Firewall on the workstation.  Do I need to permit ports on the PIX side?  If so, what are the commands?  Thanks for the inputs thus far.
0
 
ngravattCommented:
All you need to do is add a rule to the firewall that allows VPN users (whatever thier IP address range is) to have access to MAS200 on port 10000.

There will be no port confict.  The VPN user establishes a connection to the VPN concentrator using a random port as the source.  
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Increase Security & Decrease Risk with NSPM Tools

Analyst firm, Enterprise Management Associates (EMA) reveals significant benefits to enterprises when using Network Security Policy Management (NSPM) solutions, while organizations without, experienced issues including non standard security policies and failed cloud migrations

  • 4
  • 3
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now