Results 1 to 5 of 5

Thread: 1 PC, 2 Network Cards and Orientation flows

  1. #1
    Join Date
    Jun 2009
    Posts
    53

    1 PC, 2 Network Cards and Orientation flows

    Here is my problem. I have a PC with Wired Network card connected to my company network. I also have a WiFi that allows me to connect to a router for Internet. I want to know how to make everything that is Internet (Firefox sync Google Calendar, Notes ... etc) through the WiFi connection, while you can continue to use my company's applications?

    Today, if I unplug my network cable, no problem to access the Internet and synchronize, but suddenly I have access to my applications of company.

  2. #2
    Join Date
    Apr 2008
    Posts
    3,339

    Re: 1 PC, 2 Network Cards and Orientation flows

    It's simple: if you are not the admin of your computer, you could not do it. You'll need your admin and will have to ask him to open the internal network of the computer. If the answer is no, and that you estimate to need it, you ask your superior as high as you can ask to open the necessary.

  3. #3
    Join Date
    May 2008
    Posts
    551

    Re: 1 PC, 2 Network Cards and Orientation flows

    Are the two network cards connected but does not work? If not, you'll have to edit the routing table. If you want to manually specify the optimal route for IP packets or need to maintain separate default gateways, use the route command to display, add, and edit the local route tables for your Windows based computer.

  4. #4
    Join Date
    Jun 2009
    Posts
    53

    Re: 1 PC, 2 Network Cards and Orientation flows

    Actually the two connected does not worked. I had thought of editing the routing table but I do not know how to do so.

  5. #5
    Join Date
    May 2008
    Posts
    551

    Re: 1 PC, 2 Network Cards and Orientation flows

    Route

    Displays and modifies the entries in the local IP routing table. Used without parameters, route displays help.

    Syntax

    Code:
    route [-f] [-p] [Command [Destination] [mask Netmask] [Gateway] [metric Metric]] [if Interface]]
    Parameters

    -f : Clears the routing table of all entries that are not host routes (routes with a netmask of 255.255.255.255), the loopback network route (routes with a destination of 127.0.0.0 and a netmask of 255.0.0.0), or a multicast route (routes with a destination of 224.0.0.0 and a netmask of 240.0.0.0). If this is used in conjunction with one of the commands (such as add, change, or delete), the table is cleared prior to running the command.

    -p : When used with the add command, the specified route is added to the registry and is used to initialize the IP routing table whenever the TCP/IP protocol is started. By default, added routes are not preserved when the TCP/IP protocol is started. When used with the print command, the list of persistent routes is displayed. This parameter is ignored for all other commands. Persistent routes are stored in the registry location HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\PersistentRoutes.

    Destination : Specifies the network destination of the route. The destination can be an IP network address (where the host bits of the network address are set to 0), an IP address for a host route, or 0.0.0.0 for the default route.

    mask Netmask : Specifies the netmask (also known as a subnet mask) associated with the network destination. The subnet mask can be the appropriate subnet mask for an IP network address, 255.255.255.255 for a host route, or 0.0.0.0 for the default route. If omitted, the subnet mask 255.255.255.255 is used. Because of the relationship between the destination and the subnet mask in defining routes, the destination cannot be more specific than its corresponding subnet mask. In other words, there cannot be a bit set to 1 in the destination if the corresponding bit in the subnet mask is a 0.

    Gateway : Specifies the forwarding or next hop IP address over which the set of addresses defined by the network destination and subnet mask are reachable. For locally attached subnet routes, the gateway address is the IP address assigned to the interface that is attached to the subnet. For remote routes, available across one or more routers, the gateway address is a directly reachable IP address that is assigned to a neighboring router.

    metric Metric : Specifies an integer cost metric (ranging from 1 to 9999) for the route, which is used when choosing among multiple routes in the routing table that most closely match the destination address of a packet being forwarded. The route with the lowest metric is chosen. The metric can reflect the number of hops, the speed of the path, path reliability, path throughput, or administrative properties.

    if Interface : Specifies the interface index for the interface over which the destination is reachable. For a list of interfaces and their corresponding interface indexes, use the display of the route print command. You can use either decimal or hexadecimal values for the interface index. For hexadecimal values, precede the hexadecimal number with 0x. When the if parameter is omitted, the interface is determined from the gateway address.

Similar Threads

  1. Multiple Network Cards and Networks
    By akhtar in forum Windows Vista Network
    Replies: 2
    Last Post: 27-11-2009, 05:27 PM
  2. Share internet with 2 network cards
    By Pratyush in forum Technology & Internet
    Replies: 3
    Last Post: 26-03-2009, 03:04 PM
  3. Setup 2 network cards in windows 2008
    By Eric in forum Windows Server Help
    Replies: 2
    Last Post: 09-03-2009, 05:36 AM
  4. IP of the WHS with two network cards
    By Wahib in forum Networking & Security
    Replies: 3
    Last Post: 27-02-2009, 02:02 PM
  5. Speed test for network cards?
    By Aberto in forum Networking & Security
    Replies: 2
    Last Post: 26-02-2009, 03:32 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,750,221,207.03303 seconds with 16 queries