NAT configuration issue.... trying to 2 weeks but seems going no w

[Guest]

hi,
was going through NAT as i had to share internet to my office computer,
50 in nos. as i dont want to use third party proxy, i opted for NAT then ICS
as there seems to be added benifit in it. for guidance, i got the site for
help:

NAT in Windows 2003: Setup and Configuration
http://www.windowsnetworking.com/articles_tutorials/NAT_Windows_2003_Setup_Configuration.html

here, it seems that the topic has not been completely seen to. well, i did
as it was instructed in the steps. and this is the ip configuration file:

NOTE: i can browse the net in this server machine, ie windows 2003 server
std edtn, SP1.

***********************************************************

Windows IP Configuration

Host Name . . . . . . . . . . . . : win2k3
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Internet: //NIC card which links to the ISP

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82559 Fast Ethernet LAN on
Motherboard
Physical Address. . . . . . . . . : 00-03-47-10-F0-78
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.202.18.8
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . : 10.202.18.1
DNS Servers . . . . . . . . . . . : 164.100.3.1
164.100.17.3

Ethernet adapter Private Network: // named it for internal network

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8029(AS)-based Ethernet
Adapter (Generic)
Physical Address. . . . . . . . . : 00-40-33-A0-D9-19
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 164.100.3.1
164.100.17.3

************************************************************
well then, reg the client configuratin (windows xp pro SP2), i referred this
site though it dosent contain notes for XP pro,

http://support.microsoft.com/?kbid=299801

and then got this ip config details:

************************************************************
Windows IP Configuration

Host Name . . . . . . . . . . . . : node-02
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mshome.net

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : mshome.net
Description . . . . . . . . . . . : Intel(R) PRO/100+ PCI Adapter
Physical Address. . . . . . . . . : 00-90-27-3C-A8-D6
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.32.204
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.202.18.8
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Wednesday, July 12, 2006
11:22:22 AM
Lease Expires . . . . . . . . . . : Wednesday, July 19, 2006
11:22:22 AM

************************************************************
looking into this, can you pls guide me pls. have been trying hell lot to
get it work but seems that there is something that is missing. searched the
NET for whole week but just cant get the right data.

now you being the only hope, i sincerely feel that help is out there. 100%.
also, if possile do get me links to the site where it completely deals with
the setup and deployment of NAT in windows 2003 server and win xp pro clients.

also, i dont know where to put my queries for servers (2k/2k3). can u pls
give me the address pls.

regards
Nyaken

 

[Doug Sherman [MVP]]

1. The client has an incompatible IP address - it must be 192.168.0.x.

2. The client has the wrong default gateway - it must be 192.168.0.1.

3. Remove the DNS entries on the server's private NIC.

Doug Sherman
MCSE, MCSSA, MCP+I, MVP

 

[Guest]

dear sir/madam.
thanks for the prompt Re and as suggested i have configured the same but
alas!!! its still not functional.

ur suggestion is incorporated as ## rows below. may pls look into the
details and suggest the mistakes or guide me to something concrete.

********************
Servers Config:
Windows IP Configuration
Host Name . . . . . . . . . . . . : win2k3
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Internet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82559 Fast Ethernet LAN on
Motherboard
Physical Address. . . . . . . . . : 00-03-47-10-F0-78
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.202.18.8
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . : 10.202.18.1
DNS Servers . . . . . . . . . . . : 164.100.3.1
164.100.17.3

Ethernet adapter Private Network:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8029(AS)-based Ethernet
Adapter (Generic)
Physical Address. . . . . . . . . : 00-40-33-A0-D9-19
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
##3. Remove the DNS entries on the server's private NIC. hence there is no
DNS details
*******************************
Clients Config:

Windows IP Configuration
Host Name . . . . . . . . . . . . : node-02
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mshome.net

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : mshome.net
Description . . . . . . . . . . . : Intel(R) PRO/100+ PCI Adapter
Physical Address. . . . . . . . . : 00-90-27-3C-A8-D6
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
##1. The client has an incompatible IP address - it must be 192.168.0.x.
IP Address. . . . . . . . . . . . : 192.168.0.167
Subnet Mask . . . . . . . . . . . : 255.255.255.0
## 2. The client has the wrong default gateway - it must be 192.168.0.1.
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Thursday, July 13, 2006 4:29:16 PM
Lease Expires . . . . . . . . . . : Thursday, July 20, 2006 4:29:16 PM
***********************************

also to state is one point here:
in the dialog box of routing and remote access, under IP routing - general,
on the left side there is 4 rows with the following details:
-------------------------------------------------------------------------------------------
interface type ip address admin status
operational status
-------------------------------------------------------------------------------------------private network dedicated 192.168.0.1 up operational
loopback loopback 127.0.0.1 up operational
Internet dedicated 10.202.18.8 up operational
internal Internal Not available unknown Non-operationa

here the 4th row is confusing. what can it mean?????

this seems to be lengthy letter but pls help me out. it will be nice if you
link me to some site where in the setup of these is detailed.

regs
ken

 

[Guest]

Adding on::
a look into this might be of some help for me.

in the public interface connected to the internet, NAT and the basic
firewall option have also been enabled.

here, in the Services and Ports tab. there are listed services which would
be provided to users to access. is this setting necessary??? seems like there
is an option for HTTP and HTTPS service which by default is not checked. i
have not done this setting till now but would like to know if these setting
effect the service.

upon checking, say HTTPS, it opens up dialog box asking private
address(????) and there seems to be default entry of incoming port: 443 and
outgoing port:443.

does it mean that these setting are needed for clients to access the net
throgh NAT???

regs
Ken

 

[Doug Sherman [MVP]]

OK - now we need to determine whether this is a routing or just a name
resolution problem:

1. On node-02 open a command prompt and: ping 4.2.2.1 ENTER. What
happens? If you get replies, routing is OK.

2. At the command prompt: ping google.com ENTER. What happens? If
the name resolves to an IP address, name resolution is working.

Doug Sherman
MCSE, MCSA, MCP+I, MVP

dear sir/madam.
thanks for the prompt Re and as suggested i have configured the same but
alas!!! its still not functional.

ur suggestion is incorporated as ## rows below. may pls look into the
details and suggest the mistakes or guide me to something concrete.

********************
Servers Config:
Windows IP Configuration
Host Name . . . . . . . . . . . . : win2k3
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Internet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82559 Fast Ethernet LAN on
Motherboard
Physical Address. . . . . . . . . : 00-03-47-10-F0-78
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.202.18.8
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . : 10.202.18.1
DNS Servers . . . . . . . . . . . : 164.100.3.1
164.100.17.3

Ethernet adapter Private Network:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8029(AS)-based Ethernet
Adapter (Generic)
Physical Address. . . . . . . . . : 00-40-33-A0-D9-19
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
##3. Remove the DNS entries on the server's private NIC. hence there is no
DNS details
*******************************
Clients Config:

Windows IP Configuration
Host Name . . . . . . . . . . . . : node-02
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mshome.net

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : mshome.net
Description . . . . . . . . . . . : Intel(R) PRO/100+ PCI Adapter
Physical Address. . . . . . . . . : 00-90-27-3C-A8-D6
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
##1. The client has an incompatible IP address - it must be 192.168.0.x.
IP Address. . . . . . . . . . . . : 192.168.0.167
Subnet Mask . . . . . . . . . . . : 255.255.255.0
## 2. The client has the wrong default gateway - it must be 192.168.0.1.
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Thursday, July 13, 2006 4:29:16 PM
Lease Expires . . . . . . . . . . : Thursday, July 20, 2006 4:29:16 PM
***********************************

also to state is one point here:
in the dialog box of routing and remote access, under IP routing - general,
on the left side there is 4 rows with the following details:
-------------------------------------------------------------------------- -----------------
interface type ip address admin status
operational status
--------------------------------------------------------------------------

-----------------private network dedicated 192.168.0.1 up operational

 

[Doug Sherman [MVP]]

No - don't worry about the Basic Firewall for now. These settings are
to allow specified Internet traffic into your LAN.

Doug Sherman
MCSE, MCSA, MCP+I, MVP

Adding on::
a look into this might be of some help for me.

in the public interface connected to the internet, NAT and the basic
firewall option have also been enabled.

here, in the Services and Ports tab. there are listed services which would
be provided to users to access. is this setting necessary??? seems like there
is an option for HTTP and HTTPS service which by default is not checked. i
have not done this setting till now but would like to know if these setting
effect the service.

upon checking, say HTTPS, it opens up dialog box asking private
address(????) and there seems to be default entry of incoming port: 443 and
outgoing port:443.

does it mean that these setting are needed for clients to access the net
throgh NAT???

regs
Ken





--------------------------------------------------------------------------

-----------------private network dedicated 192.168.0.1 up operational

 

[Guest]

thanks for the Re:
so here is the test run result:
##1. On node-02 open a command prompt and: ping 4.2.2.1 ENTER
Result:
Pinging 4.2.2.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 4.2.2.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

##2. At the command prompt: ping google.com ENTER.
Pinging google.com [72.14.207.99] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 72.14.207.99:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

here it seems like the name resolves to IP address. hence i persume that
DNS is working. isnt it.

so what can i do to solve out this problem now. seems like am finally
heading towards the solution. a ray of hope in the end of the tunnel.

awaiting ur reply eagerly

regs
ken

 

[Doug Sherman [MVP]]

OK - routing is not working which means that RRAS NAT is not properly
configured. Probably the easiest thing to do is disable RRAS, re-enable
it, and run the wizarrd again:

http://download.microsoft.com/download/2/e/c/2ec23de9-4bc3-45a0-9127-89ec6bf
89391/connectnetwork.doc

Doug Sherman
MCSE, MCSA, MCP+I, MVP

thanks for the Re:
so here is the test run result:
##1. On node-02 open a command prompt and: ping 4.2.2.1 ENTER
Result:
Pinging 4.2.2.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 4.2.2.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

##2. At the command prompt: ping google.com ENTER.
Pinging google.com [72.14.207.99] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 72.14.207.99:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

here it seems like the name resolves to IP address. hence i persume that
DNS is working. isnt it.

so what can i do to solve out this problem now. seems like am finally
heading towards the solution. a ray of hope in the end of the tunnel.

awaiting ur reply eagerly

regs
ken

OK - now we need to determine whether this is a routing or just a name
resolution problem:

1. On node-02 open a command prompt and: ping 4.2.2.1 ENTER. What
happens? If you get replies, routing is OK.

2. At the command prompt: ping google.com ENTER. What happens? If
the name resolves to an IP address, name resolution is working.

Doug Sherman
MCSE, MCSA, MCP+I, MVP


is
no
----------------------------------------------------------------------------------------------------------------------------------------------------
-----------------private network dedicated 192.168.0.1 up operational if
you NAT
then site
for
http://www.windowsnetworking.com/articles_tutorials/NAT_Windows_2003_Setup_C well, i
did configuration
file: Ethernet
LAN on lot
to can u
pls

 

[Guest]

now this going just the same way...

sorry to say that the NAT in my server is still unfunctional. ur doc file
was very helpful and i did exactly the same way as it was written in it. then
also there seems to be some problems.

of late, after installation, i found that my antivirus, i.e web based
installed one from a remote server is working. it even takes the updates
also. and the site even works. this left me puzzled???? other site just dont
open at all.

thus it mean that NAT is working partially??? i have, as advised, disabled
the service and reconfigured many a times but the same result. i think there
will be other way to test my connectivity. other IP related i.e. DNS and DHCP
is aitoconfigued within NAT and there seems to be no problem with it.

how do i test the router. as siad ping 4.2.2.1 has not yeilded any result
yet. is there other way to acertain the functionality?

for ur info, there are something that is still puzzelling me:
##1. in RRAS dialog box->[server]->IP routing->IGMP, on the right hand side
there are the 2 interface listed and in the "state" column, it states "Non
Querier/Not Forwarding" and in "Protocol" it given as "Router V3".
##2. in the same one under "General" on the right hand side there are 4
entries: namely: [Public interface], Loopback, [Private interface] and
internal. in the internal details its written likewise:
"IP address: Not available", "Admintrative Status: Unknown", "Operational
Status: Non operational".... others.
thus this implies that internal NAT is still not functional??? all other
above 3 fields are ok and are shown as working ones.
this testing and installtion is really taking some serious toll. i never
imagined that this is that tough. if not possible, then i will have to go for
other third party ones.

pls enlighten me on this issue if u have not got really bored up.

with regs
ken

OK - routing is not working which means that RRAS NAT is not properly
configured. Probably the easiest thing to do is disable RRAS, re-enable
it, and run the wizarrd again:

http://download.microsoft.com/download/2/e/c/2ec23de9-4bc3-45a0-9127-89ec6bf
89391/connectnetwork.doc

Doug Sherman
MCSE, MCSA, MCP+I, MVP

thanks for the Re:
so here is the test run result:
##1. On node-02 open a command prompt and: ping 4.2.2.1 ENTER
Result:
Pinging 4.2.2.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 4.2.2.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

##2. At the command prompt: ping google.com ENTER.
Pinging google.com [72.14.207.99] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 72.14.207.99:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

here it seems like the name resolves to IP address. hence i persume that
DNS is working. isnt it.

so what can i do to solve out this problem now. seems like am finally
heading towards the solution. a ray of hope in the end of the tunnel.

awaiting ur reply eagerly

regs
ken

OK - now we need to determine whether this is a routing or just a name
resolution problem:

1. On node-02 open a command prompt and: ping 4.2.2.1 ENTER. What
happens? If you get replies, routing is OK.

2. At the command prompt: ping google.com ENTER. What happens? If
the name resolves to an IP address, name resolution is working.

Doug Sherman
MCSE, MCSA, MCP+I, MVP


dear sir/madam.
thanks for the prompt Re and as suggested i have configured the same but
alas!!! its still not functional.

ur suggestion is incorporated as ## rows below. may pls look into the
details and suggest the mistakes or guide me to something concrete.

********************
Servers Config:
Windows IP Configuration
Host Name . . . . . . . . . . . . : win2k3
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Internet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82559 Fast Ethernet LAN on
Motherboard
Physical Address. . . . . . . . . : 00-03-47-10-F0-78
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.202.18.8
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . : 10.202.18.1
DNS Servers . . . . . . . . . . . : 164.100.3.1
164.100.17.3

Ethernet adapter Private Network:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8029(AS)-based Ethernet
Adapter (Generic)
Physical Address. . . . . . . . . : 00-40-33-A0-D9-19
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
##3. Remove the DNS entries on the server's private NIC. hence there is
no
DNS details
*******************************
Clients Config:

Windows IP Configuration
Host Name . . . . . . . . . . . . : node-02
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mshome.net

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : mshome.net
Description . . . . . . . . . . . : Intel(R) PRO/100+ PCI Adapter
Physical Address. . . . . . . . . : 00-90-27-3C-A8-D6
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
##1. The client has an incompatible IP address - it must be
192.168.0.x.
IP Address. . . . . . . . . . . . : 192.168.0.167
Subnet Mask . . . . . . . . . . . : 255.255.255.0
## 2. The client has the wrong default gateway - it must be
192.168.0.1.
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Thursday, July 13, 2006
4:29:16 PM
Lease Expires . . . . . . . . . . : Thursday, July 20, 2006
4:29:16 PM
***********************************

also to state is one point here:
in the dialog box of routing and remote access, under IP routing -
general,
on the left side there is 4 rows with the following details:
--------------------------------------------------------------------------
-----------------
interface type ip address admin status
operational status
--------------------------------------------------------------------------
-----------------private network dedicated 192.168.0.1 up operational
loopback loopback 127.0.0.1 up operational
Internet dedicated 10.202.18.8 up operational
internal Internal Not available unknown Non-operationa

here the 4th row is confusing. what can it mean?????

this seems to be lengthy letter but pls help me out. it will be nice if
you
link me to some site where in the setup of these is detailed.

regs
ken

:

1. The client has an incompatible IP address - it must be
192.168.0.x.

2. The client has the wrong default gateway - it must be 192.168.0.1.

3. Remove the DNS entries on the server's private NIC.

Doug Sherman
MCSE, MCSSA, MCP+I, MVP

hi,
was going through NAT as i had to share internet to my office
computer,
50 in nos. as i dont want to use third party proxy, i opted for NAT
then
ICS
as there seems to be added benifit in it. for guidance, i got the site
for
help:

NAT in Windows 2003: Setup and Configuration


http://www.windowsnetworking.com/articles_tutorials/NAT_Windows_2003_Setup_C
onfiguration.html

here, it seems that the topic has not been completely seen to. well, i
did
as it was instructed in the steps. and this is the ip configuration
file:

NOTE: i can browse the net in this server machine, ie windows 2003
server
std edtn, SP1.

***********************************************************

Windows IP Configuration

Host Name . . . . . . . . . . . . : win2k3
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Internet: //NIC card which links to the ISP

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82559 Fast Ethernet
LAN on
Motherboard
Physical Address. . . . . . . . . : 00-03-47-10-F0-78
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.202.18.8
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . : 10.202.18.1
DNS Servers . . . . . . . . . . . : 164.100.3.1
164.100.17.3

Ethernet adapter Private Network: // named it for internal network

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8029(AS)-based
Ethernet
Adapter (Generic)
Physical Address. . . . . . . . . : 00-40-33-A0-D9-19
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 164.100.3.1
164.100.17.3

************************************************************
well then, reg the client configuratin (windows xp pro SP2), i
referred
this
site though it dosent contain notes for XP pro,

http://support.microsoft.com/?kbid=299801

and then got this ip config details:

************************************************************
Windows IP Configuration

Host Name . . . . . . . . . . . . : node-02
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mshome.net

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : mshome.net
Description . . . . . . . . . . . : Intel(R) PRO/100+ PCI
Adapter
Physical Address. . . . . . . . . : 00-90-27-3C-A8-D6
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.32.204
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.202.18.8
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Wednesday, July 12, 2006
11:22:22 AM
Lease Expires . . . . . . . . . . : Wednesday, July 19, 2006
11:22:22 AM

************************************************************
looking into this, can you pls guide me pls. have been trying hell lot
to
get it work but seems that there is something that is missing.
searched
the
NET for whole week but just cant get the right data.