ad <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
> Hi,
>
> I am trying to get my work windoze laptop work with my home
> network. Here is my configuration:
>
> Firewall / DHCP Server Machine:
> - debian 2.4.22 (testing)
> - dhcp for external eth0
> - static ip address: 192.168.0.1 for internal eth1 card
> - dhcp server ip range: 192.168.0.10 - 192.168.0.20
> - shorewall firewall
> - squid
> - /etc/resolv.conf
> search myISP.provider.net
> nameserver 127.0.0.1
Why localhost?
> nameserver a.b.c.d
> nameserver a.b.c.e
This is your GW machine at home. Is it MASQing your lan boxes? How
are you using squid? It provides dhcp service for the Win machine but
no others?
> Linux Client machine:
> - debian 2.4.18 (unstable)
> - static ip address: 192.168.0.2
> - /etc/resolv.conf:
> search myISP.provider.net
> nameserver 127.0.0.1
Why localhost?
>
> Windoze XP Client:
> - Obtain an IP address automatically - DHCP Enabled
> (gets 192.168.0.10)
> - Obtain DNS server address automatically
> (gets 192.168.0.10)
This part -- dns -- seems not to be set up properly in your dhcp
server. I would think it should be the same as your Linux client.
> From both clients, I can ping all the internal machine IPs fine.
They are on the same subnet -- no routing required.
> From Linux client, I can connect to the web with or without proxy
> server of the server machine without any problems. ...
What do you mean proxy server -- squid? Why are you running squid?
> ...I can ping web
> addresses such as "www.debian.org" fine as well as 192.25.206.10
> (debian.org's address).
>
> But, from the windoze machine, I can only connect to the web if I use
> the proxy address of my server machine (192.168.0.1:3128). I can NOT
> use "direct connection to internet". I also cannot ping
> "www.debian.org" nor 192.25.206.10 (debian.org's address).
This sounds like routing table is not set up properly. What is the
default (GW) route?
> The firewall setup in server machine does not have anything special
> for Linux client that windoze client doesn't get. All the internal
> machine are setup to have access to internet and proxy server in my
> server machine. ...
When trying to test fixes for this problem, be sure to flush iptables
or just turn off the FW. It's a pain bringing it down and back up
each time you test a change, but it's the best way to isolate --
eliminate -- the FW as a possible source of problems. (Which it
probably will be when you set up your tunnel).
> ...I also can not use my work place's private secure
> network tunnel program either to connect to work in this windoze
> machine.
One thing at a time. You'll need to set this up separately after you
establish your basic, desired connectivity.
> So I must be missing something. I do not want to play with any network
> setting in windoze machine since I use it at work. I tried to install
> "bind" and "pdns (a nameserver program)" into my server machine, that
> didn't change anything either.
>
> Any help will be greatly appreciated. Thanks.
Without any route table output from any machines it's really hard to
even guess without running the risk of upsetting something.
We need output from :
[linux]$ /sbin/route -n
windows> ipconfig /all
Why dhcp rather than static setup? You don't want to "touch" the
network setup on the Windows laptop for fear of disturbing the
settings? Does it use dhcp at work?
We also need to see dhcpd.conf from the dhcp server. This could get a
bit tricky, since you're getting dhcp info for this server (ip, GW
default route, and name server) and will need to relay the name server
info to your Win laptop. The Linux client's dhcp setup may be useful
-- though it's been years since I've played much with Deb ;-)
If you want some howto background for Windows networking problems you
might try here for a start:
http://support.microsoft.com/default...b;EN-US;314067
hth,
prg
email above disabled
Similar Threads
Linear Mode
