Results 1 to 7 of 7

Thread: Lan working only when i'm not connected on internet

  1. #1
    Junior Member
    Join Date
    Jan 2006
    Posts
    3

    Lan working only when i'm not connected on internet

    Hi everybody

    Sinse 3 days ago i'm trying to share my internet connection, with or withoug Wingate (or Kerio Winroute, anyway i'm not at this point yet)

    I have a pc desktop (A) under Windows XP Pro connected to a USB Speedtouch Thomson 330 modem and under Kerio Personal Firewall. I want to provide internet access to my other machine: my laptop (B) also under Windows XP Pro but without Firewall. XP Firewall is desactivated on both machines.

    My major problem is that LAN access between the two machines works fine when (A) is not connect to internet, but does'nt work when it is connected.
    I know that this certainly isn't due to Firewall because this one is always active including when i'm not connected to internet. Moreover i added to (A)'s firewall a rule allowing access to and sinse 192.168.0.2, that is (B)'s IP (mask 255.255.255.0, gateway 192.168.0.1, DNS server 192.168.0.1).

    In (B)'s local connexion properties i have IP: 192.168.0.1 mask 255.255.255.0 no gateway.

    I have allowed internet connexion share in (A)'s internet conection properties (whitch has forced me to install again Windows SP1 following recomendations of Microsoft help online website because i had a 1068 error, but this is not the point).
    I have specified in (B)'s IE properties a proxy server with IP : 192.168.0.1 port 80.

    Finally, all seems to be correctly configured but when I'm online on (A), (B) can no more access to (A)'s shared directories: when I click on (B)'s name on (B) in Favorite networks/All network/Microsoft Windows network/Workgroup/(A)'s name, i get an error message "(A) is not accessible, u maybe don't have autorisations necessary....".

    I must add that both machines can always ping each other, and resolve each other name.
    In that conditions, if I try to install Wingate on (B) for example, while Wingate Server already is installed and active on (A), (B) cannot detect the Wingate Server on (A) while process of installing.

    If anyone has an idea about what goes wrong..
    (Sorry for mistakes english is not my native language ;) )

    zigligli.

  2. #2
    Super Moderator Super Moderator Big Booger's Avatar
    Join Date
    Apr 2002
    Location
    JAPAN
    Posts
    10,660
    How are you connecting (A) and (B)? Direct cable connection? Router? Hub? Wirelessly?

  3. #3
    Junior Member
    Join Date
    Jan 2006
    Posts
    3
    oops i've forgotten this information, (A) & (B) are connected via crossed cable

  4. #4
    Super Moderator Super Moderator Big Booger's Avatar
    Join Date
    Apr 2002
    Location
    JAPAN
    Posts
    10,660
    Quote Originally Posted by zigligli
    oops i've forgotten this information, (A) & (B) are connected via crossed cable
    And (A) has 2 network cards?

    You might need to change the subnet mask to a different number, and this might fix your issue... but then again I don't know for sure.

  5. #5
    Junior Member
    Join Date
    Jan 2006
    Posts
    3
    (A) has 1 NIC

    this is his config /all 's result :

    Card Ethernet Connection local network:
    Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
    DHCP activé. . . . . . . . . . . : Non
    Adresse IP. . . . . . . . . . . . : 192.168.0.1
    Masque de sous-réseau . . . : 255.255.255.0
    Passerelle par défaut . . . . . :

    Card Ethernet Connection local network 5:
    Suffixe DNS propre à la connexion :
    Description . . . . . . . . . . . : SpeedTouch Ethernet Adapter #4
    DHCP activé. . . . . . . . . . . : Oui
    Configuration automatique activée . . . . : Oui
    Autoconfiguration d'adresse IP. . : 169.254.124.220
    Masque de sous-réseau . . . . . . : 255.255.0.0
    Passerelle par défaut . . . . . . :

    Card PPP My ISP :
    Suffixe DNS propre à la connexion :
    Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
    DHCP activé. . . . . . . . . . . : Non
    Adresse IP. . . . . . . . . . . . : 83.34.15.163
    Masque de sous-réseau . . . . . . : 255.255.255.255
    Passerelle par défaut . . . . . . : 83.34.15.163
    Serveurs DNS . . . . . . . . . . : 80.58.61.250
    80.58.61.254

    (Connection local network 5 has been created automatically during creation of the internet connection)


    now this is his route print's result when offline :

    Destination net - Mask net - Gateway - NIC
    127.0.0.0 - 255.0.0.0 - 127.0.0.1 - 127.0.0.1
    169.254.0.0 - 255.255.0.0 - 169.254.124.220 - 169.254.124.220
    169.254.124.220 - 255.255.255.255 - 127.0.0.1 - 127.0.0.1
    169.254.255.255 - 255.255.255.255 - 169.254.124.220 - 169.254.124.220
    192.168.0.0 - 255.255.255.0 - 192.168.0.1 - 192.168.0.1
    192.168.0.1 - 255.255.255.255 - 127.0.0.1 - 127.0.0.1
    192.168.0.255 - 255.255.255.255 192.168.0.1 - 192.168.0.1
    224.0.0.0 - 240.0.0.0 - 169.254.124.220 - 169.254.124.220
    224.0.0.0 - 240.0.0.0 - 192.168.0.1 - 192.168.0.1
    255.255.255.255 - 255.255.255.255 - 169.254.124.220 - 169.254.124.220
    255.255.255.255 - 255.255.255.255 - 192.168.0.1 - 192.168.0.1
    =======================================================

    and now this is the route print 's result when online :

    Destination net - Mask net - Gateway - NIC
    127.0.0.0 - 255.0.0.0 - 127.0.0.1 - 127.0.0.1
    169.254.0.0 - 255.255.0.0 - 169.254.124.220 - 169.254.124.220
    169.254.124.220 - 255.255.255.255 - 127.0.0.1 - 127.0.0.1
    169.254.255.255 - 255.255.255.255 - 169.254.124.220 - 169.254.124.220
    192.168.0.0 - 255.255.255.0 - 192.168.0.1 - 192.168.0.1
    192.168.0.1 - 255.255.255.255 - 127.0.0.1 - 127.0.0.1
    192.168.0.255 - 255.255.255.255 - 192.168.0.1 - 192.168.0.1
    224.0.0.0 - 240.0.0.0 - 169.254.124.220 - 169.254.124.220
    224.0.0.0 - 240.0.0.0 - 192.168.0.1 -192.168.0.1
    255.255.255.255 255.255.255.255 - 169.254.124.220 - 169.254.124.220
    255.255.255.255 255.255.255.255 - 192.168.0.1 - 192.168.0.1
    ======================================================
    Last edited by zigligli; January 5th, 2006 at 17:19 PM.

  6. #6
    Silver Member
    Join Date
    Oct 2004
    Location
    Ohio
    Posts
    330
    if (A) has only 1 nic then how can u conenct them via crossed cable but if ur sayin what i think u are then that means u have one onboard nic and one nic card and if u do then what u need to do is on (A) go into network connections and select both network cards and right click while both are selected and hit bridge connections that will allow u to have (A) on the internet and (B) can also read (A) and i think (B) will also have internet access because thats waht me and my friends have to do at our lan parties when there arent enough ports on the router and if u dont and truly only have one total then what i said was a waste lol but o well always good to try and help

  7. #7
    Triple Platinum Member Curio's Avatar
    Join Date
    Nov 2004
    Location
    London
    Posts
    899
    The 'personal' version of most software firewalls do not work with Windows Internet Connection Sharing. Personally I would use Windows built in firewall only with no extra software when first setting it up then try adding a third party firewall if you think you need it.
    I'm using Windows 7 - you got a problem with that?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •