• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About GeneralMandible

  • Rank
  • Birthday 10/19/1976

Contact Methods

  • Website URL
  1. For monitoring network load you can use Cacti: What is the bandwidth of the connection between the two switches (just making sure it's gig or better)? Are you sure it's the network and not the DB or disk I/O issues? Are all clients experiencing this problem? Is it just certain times of the day (peak utilization times)? Any scheduled tasks running or hung during those times? Are the disks that the DB is on almost full? On a different note: You have a network with medical records and you've tied wireless to it...why? Do you have some form of IDS running?
  2. The console connection uses a RJ45, but it is designed to connect to a serial port. By connecting it to your NIC, you're trying to talk to it with a different 'language'. If the router has an ethernet port with an IP and your NIC has an IP in the same broadcast domain, you should be able to telnet to it. A rollover cable and a crossover cable are different. A crossover generally goes from 568A to 568B ends. I believe rollover ends are pinned in reverse of each other. Of course Cisco's rollover is a DB9 on one end and a RJ45 on the other. The crossover cable is generally used for interconnecting network devices. Most newer equipment auto-senses, so you usually don't need them any more.
  3. Here's your other post: If you're just networking two computers with no shared internet connection, you can just use a crossover cable. If you insist on using the switch, connect the two computers via Cat5/5e/6 to ports on the switch. Don't connect them to the uplink one, since it is for connecting the switch to a router, broadband modem, another switch, etc. With either of these methods, you will probably need to put IP's on them manually since switches don't provide DHCP. Is this where you are needing help, setting up TCP/IP on the Windows boxes?
  4. I think what your wanting to do is channel bonding/ethernet bonding/NIC Teaming. From what I've gathered, this is a function of the NIC drivers. Do your NIC's support teaming?
  5. One thought is to install OpenSSH. This will provide you with encrypted command line access and also allow you to SFTP files. Are you wanting a separate GUI session into the system?
  6. Also, if your LAN clients are NATted behind your server, and the server and the wirless are on the same broadcast domain, wireless clients will not be able to conatct LAN clients directly. LAN clients, however, should be able to contact wireless clients (if I am understanding your topography correctly).
  7. Are the Router/WiFi and Server/LAN broadcast domains the same? If the WiFi is something like with a netmask of Then the LAN should be similar to with a netmask of Hope this helps.
  8. Do like redxii said and get a router. If you connect a switch to your ISP with 3 PC's, you will get three IP addresses from your ISP. Most ISP's only allow one IP and will bill you for using more. The router will pull one IP and provide NAT, allowing you to connect as many PC's as you want (within reason). On a side note, switches and hubs are different. Think of a switch as a cloverleaf freeway interchange and a hub as a 4-way stop.
  9. I wish and I would do so, but I don't have the MAC address - the IP address it's all I see... If you're using a Windows machine and are in the same broadcast domain, open a command prompt and type the following: ping 10.10.x.36 arp -a You should see the IP with the corresponding MAC address.
  10. I thought you could manually set the IP's for ICS?
  11. Have you disabled "Simple File Sharing:?
  12. Here is a great whitepaper on IP addressing.
  13. You can send them at a faster interval ie 10 echo requests per second. The response is a different story.
  14. Hping should be able to do that.
  15. Allow Everyone Full Control in Share permission Add Everyone to NTFS security and restrict to read and execute Enable the Guest account Run gpedit.msc Enable "Network access: Let Everyone permissions apply to anonymous users" Disable "Network access: Restrict anonymous access to Named Pipes and Shares" Remember that your Windows 2003 machine is now less secure and might be open to hackers or malware.