Página 2 de 2 PrimeiroPrimeiro 12
+ Responder ao Tópico



  1. Eles acham que profissional de TI é tudo igual, assim como por uma pessoa ser formada em Mecânica Industrial, vai saber consertar todos os motores (De carrinho de pilha até geradores nuclear)

    Citação Postado originalmente por RADER Ver Post
    Não tenho vontad de assumir o lugar, fui designado pelo Diretor da empresa, falei que nao tinha experiência, mas pra eles tanto faz, priciso do meu trabalho, ou aceito as condições ou procurar outra coisa, o que não esta fácil.

  2. Já falei para o meu supervisor que deveria ter alguém especializado na área, mas a resposta foi que a empresa tem q remanejar o que tem, precisa reduzir custos e bla bla bla.....
    mas aqui vai algumas informações da rede:
    Minha config de rede:

    auto lo
    iface lo inet loopback
    # link local(distribui)
    auto eth0
    iface eth0 inet static
    address 192.168.3.2
    netmask 255.255.255.0
    network 192.168.3.0
    broadcast 192.168.3.255

    # Link primario net
    auto eth1
    iface eth1 inet static
    address 192.168.1.253
    netmask 255.255.255.0
    network 192.168.1.5
    broadcast 192.168.1.255

    # Link secundario gvt
    auto eth2
    iface eth2 inet static
    address 192.168.2.254
    netmask 255.255.255.0
    network 192.168.2.0
    broadcast 192.168.2.255

    Dhcp:
    ddns-update-style none;
    default-lease-time 900;
    max-lease-time 9200;
    authoritative;

    subnet 192.168.3.0 netmask 255.255.255.0 {
    range 192.168.3.1 192.168.3.254;
    option routers 192.168.3.2;
    option domain-name-servers 8.8.8.8,8.8.4.4;
    option broadcast-address 192.168.3.255;
    }

    host IMPRESSORA RH {
    hardware ethernet 00:15:99:xxx;
    fixed-address 192.168.1.224;
    }

    host DLINK {
    hardware ethernet 30:B5:xxx;
    fixed-address 192.168.1.26;
    }

    host LINKSYS {
    hardware ethernet 00:1E:E5:xxx;
    fixed-address 192.168.1.76;
    }

    host BD Principal {
    hardware ethernet 74:86:7A:xxx;
    fixed-address 192.168.1.254;
    }

    host Server Publico {
    hardware ethernet 50:E5:49:xx;
    fixed-address 192.168.1.251;
    }



    *-network:0
    description: Ethernet interface
    product: RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
    vendor: Realtek Semiconductor Co., Ltd.
    physical id: 5
    bus info: pci@0000:02:05.0
    logical name: eth1
    version: 10
    serial: 00:1a:3f:xxx
    size: 100Mbit/s
    capacity: 100Mbit/s
    width: 32 bits
    clock: 33MHz
    capabilities: pm bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
    configuration: autonegotiation=on broadcast=yes driver=8139too driverversion=0.9.28 duplex=full ip=192.168.1.253 latency=32 link=yes maxlatency=64 mingnt=32 multicast=yes port=MII speed=100Mbit/s
    resources: irq:20 ioport:e100(size=256) memory:ff841100-ff8411ff memory:ff820000-ff83ffff
    *-network:1
    description: Ethernet interface
    product: DGE-528T Gigabit Ethernet Adapter
    vendor: D-Link System Inc
    physical id: 6
    bus info: pci@0000:02:06.0
    logical name: eth2
    version: 10
    serial: 1c:7e:e5:xxx
    size: 100Mbit/s
    capacity: 1Gbit/s
    width: 32 bits
    clock: 66MHz
    capabilities: pm bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
    configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full ip=192.168.2.254 latency=64 link=yes maxlatency=64 mingnt=32 multicast=yes port=MII speed=100Mbit/s
    resources: irq:21 ioport:e000(size=256) memory:ff841000-ff8410ff memory:ff800000-ff81ffff
    *-network:2
    description: Ethernet interface
    product: PRO/100 VE Network Connection
    vendor: Intel Corporation
    physical id: 8
    bus info: pci@0000:02:08.0
    logical name: eth0
    version: 01
    serial: 00:1c:c0:xxxx
    size: 10Mbit/s
    capacity: 100Mbit/s
    width: 32 bits
    clock: 33MHz
    capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
    configuration: autonegotiation=on broadcast=yes driver=e100 driverversion=3.5.24-k2-NAPI duplex=half ip=192.168.3.2 latency=32 link=no maxlatency=56 mingnt=8 multicast=yes port=MII speed=10Mbit/s
    resources: irq:20 memory:ff840000-ff840fff ioport:e200(size=64)


    ifconfig:
    eth0 Link encap:Ethernet HWaddr 00:1c:c0:xxx
    inet addr:192.168.3.2 Bcast:192.168.3.255 Mask:255.255.255.0
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

    eth1 Link encap:Ethernet HWaddr 00:1a:3xxx
    inet addr:192.168.1.253 Bcast:192.168.1.255 Mask:255.255.255.0
    inet6 addr: fe80::21a:3fff:fe8b:ddc2/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:1270256 errors:0 dropped:2186 overruns:0 frame:0
    TX packets:76038 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:170011403 (170.0 MB) TX bytes:9700234 (9.7 MB)

    eth2 Link encap:Ethernet HWaddr 1c:7e:e5:xxx
    inet addr:192.168.2.254 Bcast:192.168.2.255 Mask:255.255.255.0
    inet6 addr: fe80::1e7e:e5ff:fe2d:262f/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:217 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1112 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:75089 (75.0 KB) TX bytes:217951 (217.9 KB)

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:65536 Metric:1
    RX packets:17087 errors:0 dropped:0 overruns:0 frame:0
    TX packets:17087 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:2354892 (2.3 MB) TX bytes:2354892 (2.3 MB)

    nm-tool:
    NetworkManager Tool

    State: connected (global)

    - Device: eth0 -----------------------------------------------------------------
    Type: Wired
    Driver: e100
    State: unmanaged
    Default: no
    HW Address: 00:1C:C0:8xxxx

    Capabilities:
    Carrier Detect: yes

    Wired Properties
    Carrier: off


    - Device: eth2 -----------------------------------------------------------------
    Type: Wired
    Driver: r8169
    State: unmanaged
    Default: no
    HW Address: 1C:7E:E5:xxxx

    Capabilities:
    Carrier Detect: yes
    Speed: 100 Mb/s

    Wired Properties
    Carrier: on


    - Device: eth1 -----------------------------------------------------------------
    Type: Wired
    Driver: 8139too
    State: unmanaged
    Default: no
    HW Address: 00:1A:3F:xxxx

    Capabilities:
    Carrier Detect: yes
    Speed: 100 Mb/s

    Wired Properties
    Carrier: on


    PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
    64 bytes from 8.8.8.8: icmp_seq=1 ttl=44 time=168 ms
    64 bytes from 8.8.8.8: icmp_seq=2 ttl=44 time=172 ms
    64 bytes from 8.8.8.8: icmp_seq=3 ttl=44 time=168 ms
    64 bytes from 8.8.8.8: icmp_seq=4 ttl=44 time=168 ms

    --- 8.8.8.8 ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3004ms
    rtt min/avg/max/mdev = 168.054/169.411/172.571/1.881 ms
    root@firewall:/home/firelinux# ping -c 4 www.google.com
    PING www.google.com (173.194.118.20) 56(84) bytes of data.
    64 bytes from gru06s09-in-f20.1e100.net (173.194.118.20): icmp_seq=1 ttl=57 time=31.6 ms
    64 bytes from gru06s09-in-f20.1e100.net (173.194.118.20): icmp_seq=2 ttl=57 time=33.3 ms
    64 bytes from gru06s09-in-f20.1e100.net (173.194.118.20): icmp_seq=3 ttl=57 time=29.6 ms
    64 bytes from gru06s09-in-f20.1e100.net (173.194.118.20): icmp_seq=4 ttl=57 time=43.1 ms

    --- www.google.com ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3841ms
    rtt min/avg/max/mdev = 29.618/34.437/43.188/5.225 ms



  3. Qual é o IP do server que você não consegue alcançar das estações?

    As estação estão conectadas no Firewall, e server de BD que você quer acessar está atraz dele, né não?

    Essas configs que você postou, é do Firewall? Se sim, digita esses comandos lá, e posta o resultado:

    Código :
    route -n
    iptables-save

    Também seria interessante verificar se não tem nenhuma regra de roteamento, com o comando:

    Código :
    ip rule

    Voce tem acesso ao usuário root do firewall? Ou a algum usuário com permissão de uso do sudo?






Tópicos Similares

  1. Rede sem acesso por outro ip
    Por LINK PB no fórum Redes
    Respostas: 0
    Último Post: 14-05-2014, 08:10
  2. Rede sem Fio Ubuntu
    Por davipontocom no fórum Servidores de Rede
    Respostas: 10
    Último Post: 18-06-2009, 12:59
  3. Instalaçao Ubuntu Server (Problema acesso rede/internet)
    Por ms2222 no fórum Sistemas Operacionais
    Respostas: 5
    Último Post: 05-04-2009, 18:50
  4. Respostas: 7
    Último Post: 04-09-2007, 19:37
  5. Sem acesso externo ao Terminal Server
    Por agl77 no fórum Servidores de Rede
    Respostas: 6
    Último Post: 13-12-2006, 23:32

Visite: BR-Linux ·  VivaOLinux ·  Dicas-L