Implementing source-based routing on foundry router and maintain the communication between all connected subnets

You did not say where are your two computers. Anyway, computers should work on most subnets routes except between 10.20.30.0 and 10.20.40.0 subnet.
Static routing should be set on two computers not on routers.
Assume computer A is connected to 10.20.30.252 Router A and Computer B is connected to router B.
On Computer A, you need to add route to -inet 10.20.40.0/24 via GW 203.187.106.147, and on computer B to set rotue to -inet 10.20.30/24via GW 203.187.106.138. That is all you need.

Perhaps this will help: http://www.foundrynet.com/services/documentation/edgeIron/24G_2402CF_4802CF_User.pdf

Yes, the route table won't like the same subnet on two interfaces. I'm not sure if this would work if you didn't have "ip routing" configured... you could try turning off "ip cef" too... but i've never been able to do this on a real router.

Other option on a real router is to put both interfaces in "bridge" mode, or configure the second interface to clone the details from the first... although i've only ever done this with Dialer interfaces before.

So I guess the answer is yes... the router wants to put the route to the subnet in its route table (show ip route) and if you have two interfaces both with the same subnet, the route-path costs would be equal and identical... which is a huge issue in a networking environment.

Your PC doesn't care... it's not really routing. It's quite common to do this with a PC for the purposes of doubling bandwidth, load balancing, or having redundant links. (on the switch you would need to configure a "port-channel" to bond two ports together.)

Cheers!

please add me on yahoo messenger or mail me , let me know when ur online , my id is samrat101@yahoo.com and we will be able to resolve it sooner,,, mails takes time.

Samrat

honestly, I dont think anyone here will know how to handle this problem. Try to show this problem to a trained professional.

return, cut this configuration, but put route the her isp´s.

You can ping after this?

Can´t ping you has other problem.

Good luck!

A couple of items to check -- these will not fix the issue but may isolate the problem.

On at least one wired computer that is working and one wireless computers if possible I want you to do the following
Click Start then All Programs then Accessories then Command Prompt
In the window that opens type
ipconfig /all
press enter then record all of the following for each adapter
adapter
IP address
Subnet Mask
Default Gateway
one or more DNS addresses
The back in the window enter the following command using the default gateway from the wired connection (your router address)
ping (default gateway)
you will either get 4 timeouts -- the connection fails or 4 messages with elapsed times generally measured in ms or milliseconds.
What you are looking for in the above
Good entries base
x.y.x match each other if subnet mask is right
u should be unique for the network
Wired IP address x.y.z.u not 0.0.0.0 may be 192.168.0.u
SubNet Mask ?.?.?.? assuming 255.255.255.0
Default Gateway x.y.z.? not 0.0.0.0 may be 192.168.0.1
DNS addresses ?.?.?.? not 0.0.0.0
where at least one is not zero.
Then wireless entries should be
Wired IP address x.y.z.u not 0.0.0.0 may be 192.168.0.u
SubNet Mask same as wired
Default Gateway same as wired
DNS addresses same as wired
If these are wrong there is a configuration error either in the router or wireless adapters depending on how you want your network setup.

each connected adapter wired and each wireless should also
successfully ping the default gateway or router address
If the ipconfig is right and the wired config has successful pings, then every wireless adapter that fails has a wireless config issue.
If you are willing to work through this let me know and reply with information in a comment to this issue.
You may also want to address wireless security
First you must choose a common encryption strategy for your home network. (Yes I am assuming Home Network)
In most consumer routers you activate encryption on the wireless services of the router. After doing so you must also actiate encryption services on the wireless adapters that communicate with the wireless router. The names of the encryption services in the wireless router and wireless adapter are WPA and WEP. It is important to assure all wireless adapters to connect to the wireless router can handle the encryption chosen because the router will only perform one. There are options within each technique such as the number of bits of the keys -- the longer the better but only as long as the shortest device can support. WPA is preferable to WEP because it was designed to correct weaknesses in the WEP standard and implementation. However if there is even a single device to be connected that cannot do WPA you must do WEP or replace the device WPA in home systems often have a couple of other attribute being WPA-PSK and algorithm of TKIP -- which again every wireless adapter and the wireless router/access point must support.
To procede further in a sane manner you need to identify all wireless devices that will participate in your wireless network and determine their capablities for encryption. This is generally done searching manufacturer websites under support looking for user guides and firmware updates. Sometimes a devices capabilities in the manual require firmware updates to be true for the device. Once that is figured out the standards for your network can be set and the actual implementation can proceed. You will probably want a working wired computer to maintain access to the outside world for assistance if anything goes wrong. You also want to track your changes and know how to back things out incase things become too difficult.
If you have any additional questions or would like to a review of your plan or assistance determining a plan gather up the appropriate manufacturer's names and models and I will assist as time permits.

If you're within a network and try connecting to computers on it with the WAN public IP, it simply won't work - you must use the network IP. On an external Internet connection, it should connect fine to the public IP. If you have access to an external machine (remote desktop), or if you know of an FTP proxy, you can try it that way. I also believe http://www.webftp.co.uk/ a web based FTP client would act as somewhat of a proxy, you could try that with the public IP and see how you go.