Why does the network routing configuration change?
922876
Well at least you know enough not to post your internet facing IP address  ;)\n\nI dont understand why on internal net nic you have the gateway as 192.168.1.1? It should be x.x.x.147. You state that the internal card is DHCP, which contradicts you setting the .3 address. This is where the conflict is. You need to turn off all DHCP and use only static routes on this machine. I assume the external address (.147) is not assigned by DHCP from your ISP, but rather a dedicated address.\n\nAnother way of doing this, and probably safer, is to put a router on the ISP connection, but configure up a DMZ which will allow the static address to your server from the net. This WILL require a 2nd IP address from your ISP.\n\nPort 2 of the router should be DHCP server using NAT as 192.168.1.0/24, and should take the place of your 2nd NIC. Local workstations would be DHCP client, and would be able to get to the server as a true address on the Internet (via the DMZ). This way, you free your server from routing as well.
925871
you probably changed them to something your ISP does not understand.  You should be accepting the DHCP information from the ISP to make it work properly not setting your own.  If you ISP gave you a static address then you  have to use what they sent you.  Making up your own or randomly picking things will not work.
428686
Make sure the SSID names are the same on both computers... like WORKGROUP is what it usually defaults too. I have had problems before and loading the IPX protocol has taken care of those. Hope this helps If you are using wireless, make the SSID the same name as your Router.
1181416
reset your router, or change your router address to 192.168.2.1
175392
Your ISP could have changed their DNS server addresses.  Roadrunner did this to me recently.  I had to A) find their new DNS ip address, B) go into my network properties and update the DNS value.
356668
change your network settings
336219
If you are refering to "traceroute", then yes, it\nis part of the base OS:\n\n$ which traceroute\n/usr/sbin/traceroute\n\n[Just so we're on the same page, this is the utility that\nuses ICMP to discover the route (and latencies) that\na packet would take from one location on the net to\nanother.]
202820
The nature of the routing of the internet,
501007
Type 192.168.1.1 on your url box and hit enter. You can check your settings and change them as you please.
698270
If you changed the default admin password on the router and enabled encryption, thats a good start.\n\nYou could also set the router to only accept signals from your system by specifiying the MAC address of your NIC
271704
There are potentially several.\n\nEthernet:\n\n1. The source MAC address will change to that of the router.\n2. VLAN membership in the Ethernet header might be modified.\n\nIP:\n\n1. If the router is running NAPT, the source IP address and source port will be modified.\n2. Potentially any source IP addresses embedded in the payload might be modified depending on NAPT+ALG presence.\n2. The TTL might be decremented.\n3. The ToS bits might be modified depending on packet classification and priority assignment.\n4. Based on other changes the header checksum might be modified.
1039801
your network proxy server settings are in default mode, and the packet transfer protocol in bilaspe. correcting these issues will help you find the correct forum or at least catagory for your question,,,,which was what exactly?
1171501
A layer 3 switch will switch packets faster than a traditional router because the packet switching is done in hardware as opposed to being done in software.  \n\nThat said, if you have these servers all on the same network/subnet, you don't need either one.  Just a fast layer 2 switch.  \n\nBut if you are going to have to jump between networks/subnetworks where a router would normally be required, a layer 3 switch (a fast one) is the way to go.
50092
if one router is directly connected, it will be assigned an ip and it will make a subnet
1093966
Organizing the different legs of a network
556487
Assuming that the router is uplinked to your cisco via the ethernet, verify that the ethernet port on either device is being limited in anyway.\n\nAlso, triple-check your cisco config. Are you confident that the T1s are "bonded" properly, and that your ISP is returning traffic to you across both T1's equally? You can check this by doing a "sh int" on each T1 port and noting the incomming/outgoing bandwidth stats.
522914
There may be a problem with the configuration of your IP addresses. I've prepared the following guide for you to follow (It may seem daunting but I've tried to make it as easy to follow as possible- honest!) this should sort out your problem.\n\n1) On the main computer of the network click start > run > ipconfig\n\n2) Right click the network icon in the system tray at the bottom right of the screen and click status then properties.\n\n3) From the list choose Internet Protocol (TCP/IP), click properties\n\n4) select use the following IP Address\n\n5) in default gateway type the number that appears in the default gateway section of the ipconfig window\nin subnet mask leave it as 255.255.255.0 or whatever it is\nin IP address write the smae address as in default gateway but change the last number so if default gateway is 192.168.1.1 then IP address will be 192.168.1.2 write the default gateway in the preferred and alternate DNS server fields.\n\n6) repeat steps 2-5 on the other computers but choose a new last digit in the IP address (ie 192.168.1.3 and 192.168.1.4 etc)\n\nHope this Helps!