Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Adding a static route in Windows. 2

Status
Not open for further replies.

dreynolds20

Technical User
Apr 3, 2004
28
GB
Hi,

Long story short I am trying to setup a Blackberry Enterprise Server and my ISP has opened up port 3101 and now tells me I have to add a static route on the BES.

He said that the BES on the public domain is 193.109.81.33 and that the internal address of my router is 172.35.0.245 so on that basis I have tried to add:

route add 193.109.81.33 255.255.255.0 172.35.0.245

But this just gives me an error message:

route: bad argument

Any help would be appreciated.

Cheers

Dave

 
is it a windows server RRAS router?
if so you can add it thru the rras interface...

Aftertaf

"Solutions are not the answer." - Richard Nixon
 
No it is a Cisco router that is looked after by the ISP and I have no control over it.

He said I had to add the route to the BES machine.

 
check your original route add command...
type just route add and make sure you had the syntax ok.

check see if your BES pc can ping the 193.109.81.33 address

Aftertaf

"Solutions are not the answer." - Richard Nixon
 
I can not ping that address from the BES machine, I get destination host unreachable.

I am guessing that is why I need to add a static route.

 
The IP address you're trying to add a route to is BlackBerry's server on the Net. This shouldn't need a static route:

For outgoing traffic (BES to handhelds), you just need a default gateway for communication to the Net, and a firewall rule allowing traffic from the BES on port 3101 to 193.109.81.33.

For incoming traffic (from handhelds to the BES), your firewall needs to send traffic on port 3101 from 193.109.81.33 to the IP of your BES.

Hope this helps.

Paul
 
I do this with several of our desktops the only thing that I see wrong is that you did not put in MASK.

route add 193.109.81.33 MASK 255.255.255.0 172.35.0.245

It took me along time to figure that one out.

Doug
 
Thanks for everyones help.

I was missing the MASK from the command line and the -p for it to map it everytime.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top