|
server
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
AD, DHCP or maybe DNS problem?correct place to post this question. I have also posted on the technet windows server general newsgroup but I think this is a better forum. I have a 2003 Server Running as DHCP and DNS, I have 3 cleint computers. After adding each computer to the network I see 3 different result on each computer. I am using a 2 NIC setup and I have a switch after the server. I plan on using wireless but I see the same result with everything hard wired so lets stick with that. I have a 4 port switch that hard wires each computer. Laptop 1 - Works as expected, 1) gets IP address 2) can see the other computers on the network thorugh Windows Explorer and perform fileshare fine 3) Connects to the internet correctly. Desktop 1 - Doens't work 1) gets IP Address 2) can see the other computers on the network thorugh Windows Explorer and fileshare fine 3) NO INTERNET CONNECTION? Laptop 2 - Doesn't work 1) Gets IP Address 2) CAN'T SEE OTHER COMPUTERS OR FILESHARE, BUT I CAN PING THEM? 3) NO INTERNET CONNECTION I have tried many things. I can unplug the cable from laptop 1 and place into either desktop 1 or laptop 2 and s/ same results. I can uplug cable from Either of the non working computers and they both work in Laptop 1. So that makes me think this has nothing to do with the hardware. I'm not sure what else to tell you about, I can see Laptop 2 from the 3 Computers but can't actually open it up, but it does show up on the list of for the Domain in win explorer. As for the TCP/IP settings everything is exactly the same on each client computer. In the Computers area of Active Directory everything is the same for all three computers. Just to try it out I set up reserved leases for each NIC they work fine, each computer signs on and gets the resevered IP Address. I have no idea where to go from here, please help. Thanks in advance, Hi
- What O.S are you using for each Machine? - Are you using some proxy device that denies internet access to some users? - Can you post here the results for ipconfig /all for each machine? -- Show quoteHide quoteI hope that the information above helps you Good Luck Jorge Silva MCSA Systems Administrator "Greg P" <gsp@newsgroups.nospam> wrote in message news:DB62152E-EB19-479A-A791-A1B9C258023A@microsoft.com... > FYI: this is a double post because I want' sure which forum is was the > correct place to post this question. I have also posted on the technet > windows server general newsgroup but I think this is a better forum. > > I have a 2003 Server Running as DHCP and DNS, I have 3 cleint computers. > After adding each computer to the network I see 3 different result on each > computer. I am using a 2 NIC setup and I have a switch after the server. I > plan on using wireless but I see the same result with everything hard > wired > so lets stick with that. I have a 4 port switch that hard wires each > computer. > > Laptop 1 - Works as expected, 1) gets IP address 2) can see the other > computers on the network thorugh Windows Explorer and perform fileshare > fine > 3) Connects to the internet correctly. > > Desktop 1 - Doens't work 1) gets IP Address 2) can see the other computers > on the network thorugh Windows Explorer and fileshare fine 3) NO INTERNET > CONNECTION? > > Laptop 2 - Doesn't work 1) Gets IP Address 2) CAN'T SEE OTHER COMPUTERS OR > FILESHARE, BUT I CAN PING THEM? 3) NO INTERNET CONNECTION > > I have tried many things. I can unplug the cable from laptop 1 and place > into either desktop 1 or laptop 2 and s/ same results. I can uplug cable > from Either of the non working computers and they both work in Laptop 1. > So > that makes me think this has nothing to do with the hardware. > > I'm not sure what else to tell you about, I can see Laptop 2 from the 3 > Computers but can't actually open it up, but it does show up on the list > of > for the Domain in win explorer. > > As for the TCP/IP settings everything is exactly the same on each client > computer. > > In the Computers area of Active Directory everything is the same for all > three computers. > > Just to try it out I set up reserved leases for each NIC they work fine, > each computer signs on and gets the resevered IP Address. > > I have no idea where to go from here, please help. > > Thanks in advance, Each client machine is running Win XP Pro.
No Proxy devices. I can access the internet from the server. Ipconfig on all 4 machines: Win 2003 Server Windows IP Configuration Host Name . . . . . . . . . . . . : Nugget Primary Dns Suffix . . . . . . . : sbs.net Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : Yes WINS Proxy Enabled. . . . . . . . : Yes DNS Suffix Search List. . . . . . : sbs.net austin.rr.com Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : austin.rr.com Description . . . . . . . . . . . : NVIDIA nForce Networking Controller Physical Address. . . . . . . . . : 00-XX-8D-DB-16-XX DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : xxx.112.216.xxx Subnet Mask . . . . . . . . . . . : 255.255.240.0 Default Gateway . . . . . . . . . : 70.112.208.1 DHCP Server . . . . . . . . . . . : 10.37.160.1 DNS Servers . . . . . . . . . . . : 24.93.40.62 24.93.40.63 24.93.40.75 Lease Obtained. . . . . . . . . . : Thursday, June 08, 2006 11:20:40 AM Lease Expires . . . . . . . . . . : Thursday, June 08, 2006 1:20:40 PM Ethernet adapter Local Area Connection 2: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : D-Link DFE-530TX+ PCI Fast Ethernet Adapt er (rev.F) Physical Address. . . . . . . . . : 00-xx-46-78-02-xx DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.10.1 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : DNS Servers . . . . . . . . . . . : 192.168.10.1 Laptop 1 Windows IP Configuration Host Name . . . . . . . . . . . . : Inspiron6000 Primary Dns Suffix . . . . . . . : sbs.net Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : sbs.net sbs.net sbs.net Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : sbs.net Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated Cont roller Physical Address. . . . . . . . . : 00-XX-43-79-BA-XX Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.10.4 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.10.1 DHCP Server . . . . . . . . . . . : 192.168.10.1 DNS Servers . . . . . . . . . . . : 192.168.10.1 Primary WINS Server . . . . . . . : 192.168.10.1 Lease Obtained. . . . . . . . . . : Thursday, June 08, 2006 11:02:35 PM Lease Expires . . . . . . . . . . : Monday, January 18, 2038 10:14:07 PM Ethernet adapter Wireless Network Connection: Connection-specific DNS Suffix . : sbs.net Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2915ABG Networ k Connection Physical Address. . . . . . . . . : 00-12-F0-49-8B-CC Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.10.5 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.10.1 DHCP Server . . . . . . . . . . . : 192.168.10.1 DNS Servers . . . . . . . . . . . : 192.168.10.1 Primary WINS Server . . . . . . . : 192.168.10.1 Lease Obtained. . . . . . . . . . : Thursday, June 08, 2006 9:19:27 PM Lease Expires . . . . . . . . . . : Monday, January 18, 2038 10:14:07 PM Desktop 1 Windows IP Configuration Windows IP Configuration Host Name . . . . . . . . . . . . : GREGSDESKTOP Primary Dns Suffix . . . . . . . : sbs.net Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : sbs.net sbs.net Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : sbs.net Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connecti on Physical Address. . . . . . . . . : 00-xx-E9-D2-A6-xx Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.10.2 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.10.1 DHCP Server . . . . . . . . . . . : 192.168.10.1 DNS Servers . . . . . . . . . . . : 192.168.10.1 Primary WINS Server . . . . . . . : 192.168.10.1 Lease Obtained. . . . . . . . . . : Friday, June 09, 2006 8:12:41 AM Lease Expires . . . . . . . . . . : Monday, January 18, 2038 10:14:07 PM Laptop 2 ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : CocoLaptop Primary Dns Suffix . . . . . . . : sbs.net Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : sbs.net sbs.net Ethernet adapter Local Area Connection: Media State . . . . . . . . . . . : Media disconnected Description . . . . . . . . . . . : Broadcom 570x Gigabit Integrated Con troller Physical Address. . . . . . . . . : 00-xx-1F-BD-59-xx Ethernet adapter Wireless Network Connection 3: Connection-specific DNS Suffix . : sbs.net Description . . . . . . . . . . . : Dell Wireless WLAN 1450 Dual Band WL AN Mini-PCI Card Physical Address. . . . . . . . . : 00-xx-96-CA-5D-xx Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.10.6 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.10.1 DHCP Server . . . . . . . . . . . : 192.168.10.1 DNS Servers . . . . . . . . . . . : 192.168.10.1 Primary WINS Server . . . . . . . : 192.168.10.1 Lease Obtained. . . . . . . . . . : Friday, June 09, 2006 8:19:54 AM Lease Expires . . . . . . . . . . : Monday, January 18, 2038 10:14:07 PM Show quoteHide quote "Jorge Silva" wrote: > Hi > > - What O.S are you using for each Machine? > - Are you using some proxy device that denies internet access to some users? > - Can you post here the results for ipconfig /all for each machine? > > > -- > I hope that the information above helps you > > Good Luck > Jorge Silva > MCSA > Systems Administrator > > "Greg P" <gsp@newsgroups.nospam> wrote in message > news:DB62152E-EB19-479A-A791-A1B9C258023A@microsoft.com... > > FYI: this is a double post because I want' sure which forum is was the > > correct place to post this question. I have also posted on the technet > > windows server general newsgroup but I think this is a better forum. > > > > I have a 2003 Server Running as DHCP and DNS, I have 3 cleint computers. > > After adding each computer to the network I see 3 different result on each > > computer. I am using a 2 NIC setup and I have a switch after the server. I > > plan on using wireless but I see the same result with everything hard > > wired > > so lets stick with that. I have a 4 port switch that hard wires each > > computer. > > > > Laptop 1 - Works as expected, 1) gets IP address 2) can see the other > > computers on the network thorugh Windows Explorer and perform fileshare > > fine > > 3) Connects to the internet correctly. > > > > Desktop 1 - Doens't work 1) gets IP Address 2) can see the other computers > > on the network thorugh Windows Explorer and fileshare fine 3) NO INTERNET > > CONNECTION? > > > > Laptop 2 - Doesn't work 1) Gets IP Address 2) CAN'T SEE OTHER COMPUTERS OR > > FILESHARE, BUT I CAN PING THEM? 3) NO INTERNET CONNECTION > > > > I have tried many things. I can unplug the cable from laptop 1 and place > > into either desktop 1 or laptop 2 and s/ same results. I can uplug cable > > from Either of the non working computers and they both work in Laptop 1. > > So > > that makes me think this has nothing to do with the hardware. > > > > I'm not sure what else to tell you about, I can see Laptop 2 from the 3 > > Computers but can't actually open it up, but it does show up on the list > > of > > for the Domain in win explorer. > > > > As for the TCP/IP settings everything is exactly the same on each client > > computer. > > > > In the Computers area of Active Directory everything is the same for all > > three computers. > > > > Just to try it out I set up reserved leases for each NIC they work fine, > > each computer signs on and gets the resevered IP Address. > > > > I have no idea where to go from here, please help. > > > > Thanks in advance, > > > - You shouldn't have a multihomed DC.
check: Also, make sure the internal adapter is at the top of the binding order and that File Sharing is only bound on the internal adapter. http://support.microsoft.com/default.aspx?scid=kb;en-us;266771 Active Directory communication fails on multihomed domain controllers http://support.microsoft.com/?id=272294 Name resolution and connectivity issues on a Routing and Remote Access Server that also runs DNS or WINS http://support.microsoft.com/kb/292822 - If the machines are running SP2 you need to open the FW to File share access. - Configure the Dns server to listen only on internal adpter (Open Dns server mmc console -> Right click on Dns server -> choose properties -> goto interfaces tab -> choose only the following IP Addresses, and make sure that you only have the internal interface there) -- Show quoteHide quoteI hope that the information above helps you Good Luck Jorge Silva MCSA Systems Administrator "Greg P" <gsp@newsgroups.nospam> wrote in message news:D1DAA442-DF0E-42DC-9725-02A55AFEF4AB@microsoft.com... > Each client machine is running Win XP Pro. > > No Proxy devices. > > I can access the internet from the server. > > Ipconfig on all 4 machines: > > Win 2003 Server > > Windows IP Configuration > > Host Name . . . . . . . . . . . . : Nugget > Primary Dns Suffix . . . . . . . : sbs.net > Node Type . . . . . . . . . . . . : Unknown > IP Routing Enabled. . . . . . . . : Yes > WINS Proxy Enabled. . . . . . . . : Yes > DNS Suffix Search List. . . . . . : sbs.net > austin.rr.com > > Ethernet adapter Local Area Connection: > > Connection-specific DNS Suffix . : austin.rr.com > Description . . . . . . . . . . . : NVIDIA nForce Networking Controller > Physical Address. . . . . . . . . : 00-XX-8D-DB-16-XX > DHCP Enabled. . . . . . . . . . . : Yes > Autoconfiguration Enabled . . . . : Yes > IP Address. . . . . . . . . . . . : xxx.112.216.xxx > Subnet Mask . . . . . . . . . . . : 255.255.240.0 > Default Gateway . . . . . . . . . : 70.112.208.1 > DHCP Server . . . . . . . . . . . : 10.37.160.1 > DNS Servers . . . . . . . . . . . : 24.93.40.62 > 24.93.40.63 > 24.93.40.75 > Lease Obtained. . . . . . . . . . : Thursday, June 08, 2006 11:20:40 AM > Lease Expires . . . . . . . . . . : Thursday, June 08, 2006 1:20:40 PM > > Ethernet adapter Local Area Connection 2: > > Connection-specific DNS Suffix . : > Description . . . . . . . . . . . : D-Link DFE-530TX+ PCI Fast Ethernet > Adapt > er (rev.F) > Physical Address. . . . . . . . . : 00-xx-46-78-02-xx > DHCP Enabled. . . . . . . . . . . : No > IP Address. . . . . . . . . . . . : 192.168.10.1 > Subnet Mask . . . . . . . . . . . : 255.255.255.0 > Default Gateway . . . . . . . . . : > DNS Servers . . . . . . . . . . . : 192.168.10.1 > > Laptop 1 > > Windows IP Configuration > > Host Name . . . . . . . . . . . . : Inspiron6000 > Primary Dns Suffix . . . . . . . : sbs.net > Node Type . . . . . . . . . . . . : Hybrid > IP Routing Enabled. . . . . . . . : No > WINS Proxy Enabled. . . . . . . . : No > DNS Suffix Search List. . . . . . : sbs.net > sbs.net > sbs.net > > Ethernet adapter Local Area Connection: > > Connection-specific DNS Suffix . : sbs.net > Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated > Cont > roller > Physical Address. . . . . . . . . : 00-XX-43-79-BA-XX > Dhcp Enabled. . . . . . . . . . . : Yes > Autoconfiguration Enabled . . . . : Yes > IP Address. . . . . . . . . . . . : 192.168.10.4 > Subnet Mask . . . . . . . . . . . : 255.255.255.0 > Default Gateway . . . . . . . . . : 192.168.10.1 > DHCP Server . . . . . . . . . . . : 192.168.10.1 > DNS Servers . . . . . . . . . . . : 192.168.10.1 > Primary WINS Server . . . . . . . : 192.168.10.1 > Lease Obtained. . . . . . . . . . : Thursday, June 08, 2006 > 11:02:35 > PM > Lease Expires . . . . . . . . . . : Monday, January 18, 2038 > 10:14:07 PM > > > Ethernet adapter Wireless Network Connection: > > Connection-specific DNS Suffix . : sbs.net > Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2915ABG > Networ > k Connection > Physical Address. . . . . . . . . : 00-12-F0-49-8B-CC > Dhcp Enabled. . . . . . . . . . . : Yes > Autoconfiguration Enabled . . . . : Yes > IP Address. . . . . . . . . . . . : 192.168.10.5 > Subnet Mask . . . . . . . . . . . : 255.255.255.0 > Default Gateway . . . . . . . . . : 192.168.10.1 > DHCP Server . . . . . . . . . . . : 192.168.10.1 > DNS Servers . . . . . . . . . . . : 192.168.10.1 > Primary WINS Server . . . . . . . : 192.168.10.1 > Lease Obtained. . . . . . . . . . : Thursday, June 08, 2006 9:19:27 > PM > Lease Expires . . . . . . . . . . : Monday, January 18, 2038 > 10:14:07 PM > > > Desktop 1 > > Windows IP Configuration > > Windows IP Configuration > > Host Name . . . . . . . . . . . . : GREGSDESKTOP > Primary Dns Suffix . . . . . . . : sbs.net > Node Type . . . . . . . . . . . . : Hybrid > IP Routing Enabled. . . . . . . . : No > WINS Proxy Enabled. . . . . . . . : No > DNS Suffix Search List. . . . . . : sbs.net > sbs.net > > Ethernet adapter Local Area Connection: > > Connection-specific DNS Suffix . : sbs.net > Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network > Connecti > on > Physical Address. . . . . . . . . : 00-xx-E9-D2-A6-xx > Dhcp Enabled. . . . . . . . . . . : Yes > Autoconfiguration Enabled . . . . : Yes > IP Address. . . . . . . . . . . . : 192.168.10.2 > Subnet Mask . . . . . . . . . . . : 255.255.255.0 > Default Gateway . . . . . . . . . : 192.168.10.1 > DHCP Server . . . . . . . . . . . : 192.168.10.1 > DNS Servers . . . . . . . . . . . : 192.168.10.1 > Primary WINS Server . . . . . . . : 192.168.10.1 > Lease Obtained. . . . . . . . . . : Friday, June 09, 2006 8:12:41 > AM > Lease Expires . . . . . . . . . . : Monday, January 18, 2038 > 10:14:07 PM > > > Laptop 2 ipconfig /all > > Windows IP Configuration > > Host Name . . . . . . . . . . . . : CocoLaptop > Primary Dns Suffix . . . . . . . : sbs.net > Node Type . . . . . . . . . . . . : Hybrid > IP Routing Enabled. . . . . . . . : No > WINS Proxy Enabled. . . . . . . . : No > DNS Suffix Search List. . . . . . : sbs.net > sbs.net > > Ethernet adapter Local Area Connection: > > Media State . . . . . . . . . . . : Media disconnected > Description . . . . . . . . . . . : Broadcom 570x Gigabit > Integrated > Con > troller > Physical Address. . . . . . . . . : 00-xx-1F-BD-59-xx > > Ethernet adapter Wireless Network Connection 3: > > Connection-specific DNS Suffix . : sbs.net > Description . . . . . . . . . . . : Dell Wireless WLAN 1450 Dual > Band WL > AN Mini-PCI Card > Physical Address. . . . . . . . . : 00-xx-96-CA-5D-xx > Dhcp Enabled. . . . . . . . . . . : Yes > Autoconfiguration Enabled . . . . : Yes > IP Address. . . . . . . . . . . . : 192.168.10.6 > Subnet Mask . . . . . . . . . . . : 255.255.255.0 > Default Gateway . . . . . . . . . : 192.168.10.1 > DHCP Server . . . . . . . . . . . : 192.168.10.1 > DNS Servers . . . . . . . . . . . : 192.168.10.1 > Primary WINS Server . . . . . . . : 192.168.10.1 > Lease Obtained. . . . . . . . . . : Friday, June 09, 2006 8:19:54 > AM > Lease Expires . . . . . . . . . . : Monday, January 18, 2038 > 10:14:07 PM > > > > > "Jorge Silva" wrote: > >> Hi >> >> - What O.S are you using for each Machine? >> - Are you using some proxy device that denies internet access to some >> users? >> - Can you post here the results for ipconfig /all for each machine? >> >> >> -- >> I hope that the information above helps you >> >> Good Luck >> Jorge Silva >> MCSA >> Systems Administrator >> >> "Greg P" <gsp@newsgroups.nospam> wrote in message >> news:DB62152E-EB19-479A-A791-A1B9C258023A@microsoft.com... >> > FYI: this is a double post because I want' sure which forum is was the >> > correct place to post this question. I have also posted on the technet >> > windows server general newsgroup but I think this is a better forum. >> > >> > I have a 2003 Server Running as DHCP and DNS, I have 3 cleint >> > computers. >> > After adding each computer to the network I see 3 different result on >> > each >> > computer. I am using a 2 NIC setup and I have a switch after the >> > server. I >> > plan on using wireless but I see the same result with everything hard >> > wired >> > so lets stick with that. I have a 4 port switch that hard wires each >> > computer. >> > >> > Laptop 1 - Works as expected, 1) gets IP address 2) can see the other >> > computers on the network thorugh Windows Explorer and perform fileshare >> > fine >> > 3) Connects to the internet correctly. >> > >> > Desktop 1 - Doens't work 1) gets IP Address 2) can see the other >> > computers >> > on the network thorugh Windows Explorer and fileshare fine 3) NO >> > INTERNET >> > CONNECTION? >> > >> > Laptop 2 - Doesn't work 1) Gets IP Address 2) CAN'T SEE OTHER COMPUTERS >> > OR >> > FILESHARE, BUT I CAN PING THEM? 3) NO INTERNET CONNECTION >> > >> > I have tried many things. I can unplug the cable from laptop 1 and >> > place >> > into either desktop 1 or laptop 2 and s/ same results. I can uplug >> > cable >> > from Either of the non working computers and they both work in Laptop >> > 1. >> > So >> > that makes me think this has nothing to do with the hardware. >> > >> > I'm not sure what else to tell you about, I can see Laptop 2 from the 3 >> > Computers but can't actually open it up, but it does show up on the >> > list >> > of >> > for the Domain in win explorer. >> > >> > As for the TCP/IP settings everything is exactly the same on each >> > client >> > computer. >> > >> > In the Computers area of Active Directory everything is the same for >> > all >> > three computers. >> > >> > Just to try it out I set up reserved leases for each NIC they work >> > fine, >> > each computer signs on and gets the resevered IP Address. >> > >> > I have no idea where to go from here, please help. >> > >> > Thanks in advance, >> >> >> Jorge,
What is a multihomed DC? What do I need to change on my server to mave this work? Are you saying I shouldn't have WINS and DNS on the same computer? FYI I uninstalled WINS and see the same problem, do I need to remove some records somewhere? As for configuring the DNS as you said I already had the interfaces set to only use the local nic. As for setting the binding order the internal nic was at the top of the list. How do I check to see if file sharing is only on that NIC? I had lowered the windows firewall but there was a Norton Firewall that was preventing Laptop 2 from Filesharing. That now works. So both the desktop and Laptop 2 have the same issues. They get an IP, can perform Fielsharing but can't connect to the internet. Thanks, Greg Show quoteHide quote "Jorge Silva" wrote: > > - You shouldn't have a multihomed DC. > check: > > Also, make sure the internal adapter is at the top of the binding order and > that File Sharing is only bound on the internal adapter. > http://support.microsoft.com/default.aspx?scid=kb;en-us;266771 > > Active Directory communication fails on multihomed domain controllers > > http://support.microsoft.com/?id=272294 > > Name resolution and connectivity issues on a Routing and Remote Access > Server that also runs DNS or WINS > > http://support.microsoft.com/kb/292822 > > > - If the machines are running SP2 you need to open the FW to File share > access. > - Configure the Dns server to listen only on internal adpter (Open Dns > server mmc console -> Right click on Dns server -> choose properties -> goto > interfaces tab -> choose only the following IP Addresses, and make sure that > you only have the internal interface there) > > > -- > I hope that the information above helps you > > Good Luck > Jorge Silva > MCSA > Systems Administrator > > "Greg P" <gsp@newsgroups.nospam> wrote in message > news:D1DAA442-DF0E-42DC-9725-02A55AFEF4AB@microsoft.com... > > Each client machine is running Win XP Pro. > > > > No Proxy devices. > > > > I can access the internet from the server. > > > > Ipconfig on all 4 machines: > > > > Win 2003 Server > > > > Windows IP Configuration > > > > Host Name . . . . . . . . . . . . : Nugget > > Primary Dns Suffix . . . . . . . : sbs.net > > Node Type . . . . . . . . . . . . : Unknown > > IP Routing Enabled. . . . . . . . : Yes > > WINS Proxy Enabled. . . . . . . . : Yes > > DNS Suffix Search List. . . . . . : sbs.net > > austin.rr.com > > > > Ethernet adapter Local Area Connection: > > > > Connection-specific DNS Suffix . : austin.rr.com > > Description . . . . . . . . . . . : NVIDIA nForce Networking Controller > > Physical Address. . . . . . . . . : 00-XX-8D-DB-16-XX > > DHCP Enabled. . . . . . . . . . . : Yes > > Autoconfiguration Enabled . . . . : Yes > > IP Address. . . . . . . . . . . . : xxx.112.216.xxx > > Subnet Mask . . . . . . . . . . . : 255.255.240.0 > > Default Gateway . . . . . . . . . : 70.112.208.1 > > DHCP Server . . . . . . . . . . . : 10.37.160.1 > > DNS Servers . . . . . . . . . . . : 24.93.40.62 > > 24.93.40.63 > > 24.93.40.75 > > Lease Obtained. . . . . . . . . . : Thursday, June 08, 2006 11:20:40 AM > > Lease Expires . . . . . . . . . . : Thursday, June 08, 2006 1:20:40 PM > > > > Ethernet adapter Local Area Connection 2: > > > > Connection-specific DNS Suffix . : > > Description . . . . . . . . . . . : D-Link DFE-530TX+ PCI Fast Ethernet > > Adapt > > er (rev.F) > > Physical Address. . . . . . . . . : 00-xx-46-78-02-xx > > DHCP Enabled. . . . . . . . . . . : No > > IP Address. . . . . . . . . . . . : 192.168.10.1 > > Subnet Mask . . . . . . . . . . . : 255.255.255.0 > > Default Gateway . . . . . . . . . : > > DNS Servers . . . . . . . . . . . : 192.168.10.1 > > > > Laptop 1 > > > > Windows IP Configuration > > > > Host Name . . . . . . . . . . . . : Inspiron6000 > > Primary Dns Suffix . . . . . . . : sbs.net > > Node Type . . . . . . . . . . . . : Hybrid > > IP Routing Enabled. . . . . . . . : No > > WINS Proxy Enabled. . . . . . . . : No > > DNS Suffix Search List. . . . . . : sbs.net > > sbs.net > > sbs.net > > > > Ethernet adapter Local Area Connection: > > > > Connection-specific DNS Suffix . : sbs.net > > Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated > > Cont > > roller > > Physical Address. . . . . . . . . : 00-XX-43-79-BA-XX > > Dhcp Enabled. . . . . . . . . . . : Yes > > Autoconfiguration Enabled . . . . : Yes > > IP Address. . . . . . . . . . . . : 192.168.10.4 > > Subnet Mask . . . . . . . . . . . : 255.255.255.0 > > Default Gateway . . . . . . . . . : 192.168.10.1 > > DHCP Server . . . . . . . . . . . : 192.168.10.1 > > DNS Servers . . . . . . . . . . . : 192.168.10.1 > > Primary WINS Server . . . . . . . : 192.168.10.1 > > Lease Obtained. . . . . . . . . . : Thursday, June 08, 2006 > > 11:02:35 > > PM > > Lease Expires . . . . . . . . . . : Monday, January 18, 2038 > > 10:14:07 PM > > > > > > Ethernet adapter Wireless Network Connection: > > > > Connection-specific DNS Suffix . : sbs.net > > Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2915ABG > > Networ > > k Connection > > Physical Address. . . . . . . . . : 00-12-F0-49-8B-CC > > Dhcp Enabled. . . . . . . . . . . : Yes > > Autoconfiguration Enabled . . . . : Yes > > IP Address. . . . . . . . . . . . : 192.168.10.5 > > Subnet Mask . . . . . . . . . . . : 255.255.255.0 > > Default Gateway . . . . . . . . . : 192.168.10.1 > > DHCP Server . . . . . . . . . . . : 192.168.10.1 > > DNS Servers . . . . . . . . . . . : 192.168.10.1 > > Primary WINS Server . . . . . . . : 192.168.10.1 > > Lease Obtained. . . . . . . . . . : Thursday, June 08, 2006 9:19:27 > > PM > > Lease Expires . . . . . . . . . . : Monday, January 18, 2038 > > 10:14:07 PM > > > > > > Desktop 1 > > > > Windows IP Configuration > > > > Windows IP Configuration > > > > Host Name . . . . . . . . . . . . : GREGSDESKTOP > > Primary Dns Suffix . . . . . . . : sbs.net > > Node Type . . . . . . . . . . . . : Hybrid > > IP Routing Enabled. . . . . . . . : No > > WINS Proxy Enabled. . . . . . . . : No > > DNS Suffix Search List. . . . . . : sbs.net > > sbs.net > > > > Ethernet adapter Local Area Connection: > > > > Connection-specific DNS Suffix . : sbs.net > > Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network > > Connecti > > on > > Physical Address. . . . . . . . . : 00-xx-E9-D2-A6-xx > > Dhcp Enabled. . . . . . . . . . . : Yes > > Autoconfiguration Enabled . . . . : Yes > > IP Address. . . . . . . . . . . . : 192.168.10.2 > > Subnet Mask . . . . . . . . . . . : 255.255.255.0 > > Default Gateway . . . . . . . . . : 192.168.10.1 > > DHCP Server . . . . . . . . . . . : 192.168.10.1 > > DNS Servers . . . . . . . . . . . : 192.168.10.1 > > Primary WINS Server . . . . . . . : 192.168.10.1 > > Lease Obtained. . . . . . . . . . : Friday, June 09, 2006 8:12:41 > > AM > > Lease Expires . . . . . . . . . . : Monday, January 18, 2038 > > 10:14:07 PM > > > > > > Laptop 2 ipconfig /all > > > > Windows IP Configuration > > > > Host Name . . . . . . . . . . . . : CocoLaptop > > Primary Dns Suffix . . . . . . . : sbs.net > > Node Type . . . . . . . . . . . . : Hybrid > > IP Routing Enabled. . . . . . . . : No > > WINS Proxy Enabled. . . . . . . . : No > > DNS Suffix Search List. . . . . . : sbs.net > > sbs.net > > > > Ethernet adapter Local Area Connection: > > > > Media State . . . . . . . . . . . : Media disconnected > > Description . . . . . . . . . . . : Broadcom 570x Gigabit > > Integrated > > Con > > troller > > Physical Address. . . . . . . . . : 00-xx-1F-BD-59-xx > > > > Ethernet adapter Wireless Network Connection 3: > > > > Connection-specific DNS Suffix . : sbs.net > > Description . . . . . . . . . . . : Dell Wireless WLAN 1450 Dual > > Band WL > > AN Mini-PCI Card > > Physical Address. . . . . . . . . : 00-xx-96-CA-5D-xx > > Dhcp Enabled. . . . . . . . . . . : Yes > > Autoconfiguration Enabled . . . . : Yes > > IP Address. . . . . . . . . . . . : 192.168.10.6 > > Subnet Mask . . . . . . . . . . . : 255.255.255.0 > > Default Gateway . . . . . . . . . : 192.168.10.1 > > DHCP Server . . . . . . . . . . . : 192.168.10.1 > > DNS Servers . . . . . . . . . . . : 192.168.10.1 > > Primary WINS Server . . . . . . . : 192.168.10.1 > > Lease Obtained. . . . . . . . . . : Friday, June 09, 2006 8:19:54 > > AM > > Lease Expires . . . . . . . . . . : Monday, January 18, 2038 > > 10:14:07 PM > > > > > > > > > > "Jorge Silva" wrote: > > > >> Hi > >> > >> - What O.S are you using for each Machine? > >> - Are you using some proxy device that denies internet access to some > >> users? > >> - Can you post here the results for ipconfig /all for each machine? > >> > >> > >> -- > >> I hope that the information above helps you > >> > >> Good Luck > >> Jorge Silva > >> MCSA > >> Systems Administrator > >> > >> "Greg P" <gsp@newsgroups.nospam> wrote in message > >> news:DB62152E-EB19-479A-A791-A1B9C258023A@microsoft.com... > >> > FYI: this is a double post because I want' sure which forum is was the > >> > correct place to post this question. I have also posted on the technet > >> > windows server general newsgroup but I think this is a better forum. > >> > > >> > I have a 2003 Server Running as DHCP and DNS, I have 3 cleint > >> > computers. > >> > After adding each computer to the network I see 3 different result on > >> > each > >> > computer. I am using a 2 NIC setup and I have a switch after the > >> > server. I > >> > plan on using wireless but I see the same result with everything hard > >> > wired > >> > so lets stick with that. I have a 4 port switch that hard wires each > >> > computer. > >> > > >> > Laptop 1 - Works as expected, 1) gets IP address 2) can see the other > >> > computers on the network thorugh Windows Explorer and perform fileshare > >> > fine > >> > 3) Connects to the internet correctly. > >> > > >> > Desktop 1 - Doens't work 1) gets IP Address 2) can see the other > >> > computers > >> > on the network thorugh Windows Explorer and fileshare fine 3) NO > >> > INTERNET > >> > CONNECTION? > >> > > >> > Laptop 2 - Doesn't work 1) Gets IP Address 2) CAN'T SEE OTHER COMPUTERS > >> > OR > >> > FILESHARE, BUT I CAN PING THEM? 3) NO INTERNET CONNECTION > >> > > >> > I have tried many things. I can unplug the cable from laptop 1 and > >> > place > >> > into either desktop 1 or laptop 2 and s/ same results. I can uplug > >> > cable > >> > from Either of the non working computers and they both work in Laptop > >> > 1. > >> > So > >> > that makes me think this has nothing to do with the hardware. > >> > > >> > I'm not sure what else to tell you about, I can see Laptop 2 from the 3 > >> > Computers but can't actually open it up, but it does show up on the > >> > list > >> > of > >> > for the Domain in win explorer. > >> > > >> > As for the TCP/IP settings everything is exactly the same on each > >> > client > >> > computer. > >> > > >> > In the Computers area of Active Directory everything is the same for > >> > all > >> > three computers. > >> > > >> > Just to try it out I set up reserved leases for each NIC they work > >> > fine, > >> > each computer signs on and gets the resevered IP Address. > >> > > >> > I have no idea where to go from here, please help. > >> > > >> > Thanks in advance, In line
> What is a multihomed DC? Is a Domain controller with more than one Nic (Network Interface Card) card> What do I need to change on my server to mave this work? Well you said that now you have everything working except Internet, and you also said that you don't have Proxy or any other thing that prevents/restricts users to access to the internet, so you must have a DNS resolution problem. - Do you have Forwarding enabled in the Dns server? If no go to the Dns console -> right click Dns server choose properties -> select forwarders tab -> Select All other Domains -> got to the Selected domain's forwarder Ipaddress list and place the ISP Dns server address -> click add -> restart Dns service. Test the resolution on the DC - Go to command prompt and type ping www.microsoft.com - check if returns the Ipaddress of the site, then go to the clients and check if the ping command returns the Ipaddress of the site. > Are you saying I shouldn't have WINS and DNS on the same computer? No. What I said was in a Multihomed DC you could have problems with Wins and Dns. > FYI I uninstalled WINS and see the same problem, do I need to remove some You'll only need WINS if you're using any APP in your network that needs > records somewhere? NetBIOS resolution or if you have the need to browse over different subnets using for example Network Places. > As for configuring the DNS as you said I already had the interfaces set to - Great> only use the local Nic. > As for setting the binding order the internal Nic was at the top of the - Right click on it and choose properties then you should have the "File and > list. How do I check to see if file sharing is only on that NIC? Print Sharing for Microsoft Networks Selected"; however you should disable/deselect this on the Public Interface (Security purposes). > I had lowered the windows firewall but there was a Norton Firewall that Check also if is preventing Internet access or any other access to server or > was > preventing Laptop 2 from Filesharing. That now works. So both the > desktop > and Laptop 2 have the same issues. They get an IP, can perform > Fielsharing > but can't connect to the internet. Dns, etc. Best practices here are for test DISABLE the Norton Firewall and test, in this way you can immediately check if this as relation with your current problems. -- Show quoteHide quoteI hope that the information above helps you Good Luck Jorge Silva MCSA Systems Administrator "Greg P" <gsp@newsgroups.nospam> wrote in message news:25530004-70F9-484D-A87A-26A6B823685F@microsoft.com... > Jorge, > > What is a multihomed DC? What do I need to change on my server to mave > this > work? Are you saying I shouldn't have WINS and DNS on the same computer? > FYI I uninstalled WINS and see the same problem, do I need to remove some > records somewhere? > > As for configuring the DNS as you said I already had the interfaces set to > only use the local nic. > > As for setting the binding order the internal nic was at the top of the > list. How do I check to see if file sharing is only on that NIC? > > I had lowered the windows firewall but there was a Norton Firewall that > was > preventing Laptop 2 from Filesharing. That now works. So both the > desktop > and Laptop 2 have the same issues. They get an IP, can perform > Fielsharing > but can't connect to the internet. > > Thanks, > Greg > > "Jorge Silva" wrote: > >> >> - You shouldn't have a multihomed DC. >> check: >> >> Also, make sure the internal adapter is at the top of the binding order >> and >> that File Sharing is only bound on the internal adapter. >> http://support.microsoft.com/default.aspx?scid=kb;en-us;266771 >> >> Active Directory communication fails on multihomed domain controllers >> >> http://support.microsoft.com/?id=272294 >> >> Name resolution and connectivity issues on a Routing and Remote Access >> Server that also runs DNS or WINS >> >> http://support.microsoft.com/kb/292822 >> >> >> - If the machines are running SP2 you need to open the FW to File share >> access. >> - Configure the Dns server to listen only on internal adpter (Open Dns >> server mmc console -> Right click on Dns server -> choose properties -> >> goto >> interfaces tab -> choose only the following IP Addresses, and make sure >> that >> you only have the internal interface there) >> >> >> -- >> I hope that the information above helps you >> >> Good Luck >> Jorge Silva >> MCSA >> Systems Administrator >> >> "Greg P" <gsp@newsgroups.nospam> wrote in message >> news:D1DAA442-DF0E-42DC-9725-02A55AFEF4AB@microsoft.com... >> > Each client machine is running Win XP Pro. >> > >> > No Proxy devices. >> > >> > I can access the internet from the server. >> > >> > Ipconfig on all 4 machines: >> > >> > Win 2003 Server >> > >> > Windows IP Configuration >> > >> > Host Name . . . . . . . . . . . . : Nugget >> > Primary Dns Suffix . . . . . . . : sbs.net >> > Node Type . . . . . . . . . . . . : Unknown >> > IP Routing Enabled. . . . . . . . : Yes >> > WINS Proxy Enabled. . . . . . . . : Yes >> > DNS Suffix Search List. . . . . . : sbs.net >> > austin.rr.com >> > >> > Ethernet adapter Local Area Connection: >> > >> > Connection-specific DNS Suffix . : austin.rr.com >> > Description . . . . . . . . . . . : NVIDIA nForce Networking >> > Controller >> > Physical Address. . . . . . . . . : 00-XX-8D-DB-16-XX >> > DHCP Enabled. . . . . . . . . . . : Yes >> > Autoconfiguration Enabled . . . . : Yes >> > IP Address. . . . . . . . . . . . : xxx.112.216.xxx >> > Subnet Mask . . . . . . . . . . . : 255.255.240.0 >> > Default Gateway . . . . . . . . . : 70.112.208.1 >> > DHCP Server . . . . . . . . . . . : 10.37.160.1 >> > DNS Servers . . . . . . . . . . . : 24.93.40.62 >> > 24.93.40.63 >> > 24.93.40.75 >> > Lease Obtained. . . . . . . . . . : Thursday, June 08, 2006 11:20:40 >> > AM >> > Lease Expires . . . . . . . . . . : Thursday, June 08, 2006 1:20:40 >> > PM >> > >> > Ethernet adapter Local Area Connection 2: >> > >> > Connection-specific DNS Suffix . : >> > Description . . . . . . . . . . . : D-Link DFE-530TX+ PCI Fast >> > Ethernet >> > Adapt >> > er (rev.F) >> > Physical Address. . . . . . . . . : 00-xx-46-78-02-xx >> > DHCP Enabled. . . . . . . . . . . : No >> > IP Address. . . . . . . . . . . . : 192.168.10.1 >> > Subnet Mask . . . . . . . . . . . : 255.255.255.0 >> > Default Gateway . . . . . . . . . : >> > DNS Servers . . . . . . . . . . . : 192.168.10.1 >> > >> > Laptop 1 >> > >> > Windows IP Configuration >> > >> > Host Name . . . . . . . . . . . . : Inspiron6000 >> > Primary Dns Suffix . . . . . . . : sbs.net >> > Node Type . . . . . . . . . . . . : Hybrid >> > IP Routing Enabled. . . . . . . . : No >> > WINS Proxy Enabled. . . . . . . . : No >> > DNS Suffix Search List. . . . . . : sbs.net >> > sbs.net >> > sbs.net >> > >> > Ethernet adapter Local Area Connection: >> > >> > Connection-specific DNS Suffix . : sbs.net >> > Description . . . . . . . . . . . : Broadcom 440x 10/100 >> > Integrated >> > Cont >> > roller >> > Physical Address. . . . . . . . . : 00-XX-43-79-BA-XX >> > Dhcp Enabled. . . . . . . . . . . : Yes >> > Autoconfiguration Enabled . . . . : Yes >> > IP Address. . . . . . . . . . . . : 192.168.10.4 >> > Subnet Mask . . . . . . . . . . . : 255.255.255.0 >> > Default Gateway . . . . . . . . . : 192.168.10.1 >> > DHCP Server . . . . . . . . . . . : 192.168.10.1 >> > DNS Servers . . . . . . . . . . . : 192.168.10.1 >> > Primary WINS Server . . . . . . . : 192.168.10.1 >> > Lease Obtained. . . . . . . . . . : Thursday, June 08, 2006 >> > 11:02:35 >> > PM >> > Lease Expires . . . . . . . . . . : Monday, January 18, 2038 >> > 10:14:07 PM >> > >> > >> > Ethernet adapter Wireless Network Connection: >> > >> > Connection-specific DNS Suffix . : sbs.net >> > Description . . . . . . . . . . . : Intel(R) PRO/Wireless >> > 2915ABG >> > Networ >> > k Connection >> > Physical Address. . . . . . . . . : 00-12-F0-49-8B-CC >> > Dhcp Enabled. . . . . . . . . . . : Yes >> > Autoconfiguration Enabled . . . . : Yes >> > IP Address. . . . . . . . . . . . : 192.168.10.5 >> > Subnet Mask . . . . . . . . . . . : 255.255.255.0 >> > Default Gateway . . . . . . . . . : 192.168.10.1 >> > DHCP Server . . . . . . . . . . . : 192.168.10.1 >> > DNS Servers . . . . . . . . . . . : 192.168.10.1 >> > Primary WINS Server . . . . . . . : 192.168.10.1 >> > Lease Obtained. . . . . . . . . . : Thursday, June 08, 2006 >> > 9:19:27 >> > PM >> > Lease Expires . . . . . . . . . . : Monday, January 18, 2038 >> > 10:14:07 PM >> > >> > >> > Desktop 1 >> > >> > Windows IP Configuration >> > >> > Windows IP Configuration >> > >> > Host Name . . . . . . . . . . . . : GREGSDESKTOP >> > Primary Dns Suffix . . . . . . . : sbs.net >> > Node Type . . . . . . . . . . . . : Hybrid >> > IP Routing Enabled. . . . . . . . : No >> > WINS Proxy Enabled. . . . . . . . : No >> > DNS Suffix Search List. . . . . . : sbs.net >> > sbs.net >> > >> > Ethernet adapter Local Area Connection: >> > >> > Connection-specific DNS Suffix . : sbs.net >> > Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network >> > Connecti >> > on >> > Physical Address. . . . . . . . . : 00-xx-E9-D2-A6-xx >> > Dhcp Enabled. . . . . . . . . . . : Yes >> > Autoconfiguration Enabled . . . . : Yes >> > IP Address. . . . . . . . . . . . : 192.168.10.2 >> > Subnet Mask . . . . . . . . . . . : 255.255.255.0 >> > Default Gateway . . . . . . . . . : 192.168.10.1 >> > DHCP Server . . . . . . . . . . . : 192.168.10.1 >> > DNS Servers . . . . . . . . . . . : 192.168.10.1 >> > Primary WINS Server . . . . . . . : 192.168.10.1 >> > Lease Obtained. . . . . . . . . . : Friday, June 09, 2006 >> > 8:12:41 >> > AM >> > Lease Expires . . . . . . . . . . : Monday, January 18, 2038 >> > 10:14:07 PM >> > >> > >> > Laptop 2 ipconfig /all >> > >> > Windows IP Configuration >> > >> > Host Name . . . . . . . . . . . . : CocoLaptop >> > Primary Dns Suffix . . . . . . . : sbs.net >> > Node Type . . . . . . . . . . . . : Hybrid >> > IP Routing Enabled. . . . . . . . : No >> > WINS Proxy Enabled. . . . . . . . : No >> > DNS Suffix Search List. . . . . . : sbs.net >> > sbs.net >> > >> > Ethernet adapter Local Area Connection: >> > >> > Media State . . . . . . . . . . . : Media disconnected >> > Description . . . . . . . . . . . : Broadcom 570x Gigabit >> > Integrated >> > Con >> > troller >> > Physical Address. . . . . . . . . : 00-xx-1F-BD-59-xx >> > >> > Ethernet adapter Wireless Network Connection 3: >> > >> > Connection-specific DNS Suffix . : sbs.net >> > Description . . . . . . . . . . . : Dell Wireless WLAN 1450 Dual >> > Band WL >> > AN Mini-PCI Card >> > Physical Address. . . . . . . . . : 00-xx-96-CA-5D-xx >> > Dhcp Enabled. . . . . . . . . . . : Yes >> > Autoconfiguration Enabled . . . . : Yes >> > IP Address. . . . . . . . . . . . : 192.168.10.6 >> > Subnet Mask . . . . . . . . . . . : 255.255.255.0 >> > Default Gateway . . . . . . . . . : 192.168.10.1 >> > DHCP Server . . . . . . . . . . . : 192.168.10.1 >> > DNS Servers . . . . . . . . . . . : 192.168.10.1 >> > Primary WINS Server . . . . . . . : 192.168.10.1 >> > Lease Obtained. . . . . . . . . . : Friday, June 09, 2006 >> > 8:19:54 >> > AM >> > Lease Expires . . . . . . . . . . : Monday, January 18, 2038 >> > 10:14:07 PM >> > >> > >> > >> > >> > "Jorge Silva" wrote: >> > >> >> Hi >> >> >> >> - What O.S are you using for each Machine? >> >> - Are you using some proxy device that denies internet access to some >> >> users? >> >> - Can you post here the results for ipconfig /all for each machine? >> >> >> >> >> >> -- >> >> I hope that the information above helps you >> >> >> >> Good Luck >> >> Jorge Silva >> >> MCSA >> >> Systems Administrator >> >> >> >> "Greg P" <gsp@newsgroups.nospam> wrote in message >> >> news:DB62152E-EB19-479A-A791-A1B9C258023A@microsoft.com... >> >> > FYI: this is a double post because I want' sure which forum is was >> >> > the >> >> > correct place to post this question. I have also posted on the >> >> > technet >> >> > windows server general newsgroup but I think this is a better forum. >> >> > >> >> > I have a 2003 Server Running as DHCP and DNS, I have 3 cleint >> >> > computers. >> >> > After adding each computer to the network I see 3 different result >> >> > on >> >> > each >> >> > computer. I am using a 2 NIC setup and I have a switch after the >> >> > server. I >> >> > plan on using wireless but I see the same result with everything >> >> > hard >> >> > wired >> >> > so lets stick with that. I have a 4 port switch that hard wires each >> >> > computer. >> >> > >> >> > Laptop 1 - Works as expected, 1) gets IP address 2) can see the >> >> > other >> >> > computers on the network thorugh Windows Explorer and perform >> >> > fileshare >> >> > fine >> >> > 3) Connects to the internet correctly. >> >> > >> >> > Desktop 1 - Doens't work 1) gets IP Address 2) can see the other >> >> > computers >> >> > on the network thorugh Windows Explorer and fileshare fine 3) NO >> >> > INTERNET >> >> > CONNECTION? >> >> > >> >> > Laptop 2 - Doesn't work 1) Gets IP Address 2) CAN'T SEE OTHER >> >> > COMPUTERS >> >> > OR >> >> > FILESHARE, BUT I CAN PING THEM? 3) NO INTERNET CONNECTION >> >> > >> >> > I have tried many things. I can unplug the cable from laptop 1 and >> >> > place >> >> > into either desktop 1 or laptop 2 and s/ same results. I can uplug >> >> > cable >> >> > from Either of the non working computers and they both work in >> >> > Laptop >> >> > 1. >> >> > So >> >> > that makes me think this has nothing to do with the hardware. >> >> > >> >> > I'm not sure what else to tell you about, I can see Laptop 2 from >> >> > the 3 >> >> > Computers but can't actually open it up, but it does show up on the >> >> > list >> >> > of >> >> > for the Domain in win explorer. >> >> > >> >> > As for the TCP/IP settings everything is exactly the same on each >> >> > client >> >> > computer. >> >> > >> >> > In the Computers area of Active Directory everything is the same for >> >> > all >> >> > three computers. >> >> > >> >> > Just to try it out I set up reserved leases for each NIC they work >> >> > fine, >> >> > each computer signs on and gets the resevered IP Address. >> >> > >> >> > I have no idea where to go from here, please help. >> >> > >> >> > Thanks in advance, Jorge,
Unfortunately I’m in the same spot that I started in, except we solved the file sharing issue on Laptop 2 by lowering the Norton firewall. I still can’t access the internet on the desktop or laptop 2, even though they are on the dame domain as Laptop 1 which can access the internet. With that being said I'm not sure if you still think this is a DNS problem? >Well you said that now you have everything working except Internet, and you also said that you don't have Proxy or any other thing that prevents/restricts users to access to the internet, so you must have a DNS resolution problem. >Do you have Forwarding enabled in the Dns server? Yes, this is set up with the correct ip addresses.>Test the resolution on the DC - Go to command prompt and type ping www.microsoft.com - check if returns the Ipaddress of the site then go to the clients and check if the ping command returns the Ipaddress of the site. All resolve the IP address, all requests time out. >Right click on it and choose properties then you should have the "File and Print Sharing for Microsoft Networks Selected"; however you should disable/deselect this on the Public Interface (Security purposes). The File and Print Sharing was selected previously. (there wasn’t a Public Interface option for this nic, there are only 4 options in the properties page, Client for MS Networks, Network Lad Balancing, File and Printer Sharing, and TCP/IP) >Check also if is preventing Internet access or any other access to server or Dns, etc. Best practices here are for test DISABLE the Norton Firewall and test, in this way you can immediately check if this as relation with your current problems. I uninstalled Norton totally from the desktop. If it can’t connect to the internet I can’t get a virus :) Show quoteHide quote "Jorge Silva" wrote: > In line > > > > > What is a multihomed DC? > > > > Is a Domain controller with more than one Nic (Network Interface Card) card > > > > > What do I need to change on my server to mave this work? > > > > Well you said that now you have everything working except Internet, and you > also said that you don't have Proxy or any other thing that > prevents/restricts users to access to the internet, so you must have a DNS > resolution problem. > > > > - Do you have Forwarding enabled in the Dns server? If no go to the Dns > console -> right click Dns server choose properties -> select forwarders > tab -> Select All other Domains -> got to the Selected domain's forwarder > Ipaddress list and place the ISP Dns server address -> click add -> restart > Dns service. > > > > Test the resolution on the DC - Go to command prompt and type ping > www.microsoft.com - check if returns the Ipaddress of the site, then go to > the clients and check if the ping command returns the Ipaddress of the site. > > > > > Are you saying I shouldn't have WINS and DNS on the same computer? > > > > No. What I said was in a Multihomed DC you could have problems with Wins and > Dns. > > > > FYI I uninstalled WINS and see the same problem, do I need to remove some > > records somewhere? > > > > You'll only need WINS if you're using any APP in your network that needs > NetBIOS resolution or if you have the need to browse over different subnets > using for example Network Places. > > > > > As for configuring the DNS as you said I already had the interfaces set to > > only use the local Nic. > > > > - Great > > > > As for setting the binding order the internal Nic was at the top of the > > list. How do I check to see if file sharing is only on that NIC? > > > > - Right click on it and choose properties then you should have the "File and > Print Sharing for Microsoft Networks Selected"; however you should > disable/deselect this on the Public Interface (Security purposes). > > > > I had lowered the windows firewall but there was a Norton Firewall that > > was > > preventing Laptop 2 from Filesharing. That now works. So both the > > desktop > > and Laptop 2 have the same issues. They get an IP, can perform > > Fielsharing > > but can't connect to the internet. > > > > Check also if is preventing Internet access or any other access to server or > Dns, etc. Best practices here are for test DISABLE the Norton Firewall and > test, in this way you can immediately check if this as relation with your > current problems. > > > > -- > I hope that the information above helps you > > Good Luck > Jorge Silva > MCSA > Systems Administrator > > "Greg P" <gsp@newsgroups.nospam> wrote in message > news:25530004-70F9-484D-A87A-26A6B823685F@microsoft.com... > > Jorge, > > > > What is a multihomed DC? What do I need to change on my server to mave > > this > > work? Are you saying I shouldn't have WINS and DNS on the same computer? > > FYI I uninstalled WINS and see the same problem, do I need to remove some > > records somewhere? > > > > As for configuring the DNS as you said I already had the interfaces set to > > only use the local nic. > > > > As for setting the binding order the internal nic was at the top of the > > list. How do I check to see if file sharing is only on that NIC? > > > > I had lowered the windows firewall but there was a Norton Firewall that > > was > > preventing Laptop 2 from Filesharing. That now works. So both the > > desktop > > and Laptop 2 have the same issues. They get an IP, can perform > > Fielsharing > > but can't connect to the internet. > > > > Thanks, > > Greg > > > > "Jorge Silva" wrote: > > > >> > >> - You shouldn't have a multihomed DC. > >> check: > >> > >> Also, make sure the internal adapter is at the top of the binding order > >> and > >> that File Sharing is only bound on the internal adapter. > >> http://support.microsoft.com/default.aspx?scid=kb;en-us;266771 > >> > >> Active Directory communication fails on multihomed domain controllers > >> > >> http://support.microsoft.com/?id=272294 > >> > >> Name resolution and connectivity issues on a Routing and Remote Access > >> Server that also runs DNS or WINS > >> > >> http://support.microsoft.com/kb/292822 > >> > >> > >> - If the machines are running SP2 you need to open the FW to File share > >> access. > >> - Configure the Dns server to listen only on internal adpter (Open Dns > >> server mmc console -> Right click on Dns server -> choose properties -> > >> goto > >> interfaces tab -> choose only the following IP Addresses, and make sure > >> that > >> you only have the internal interface there) > >> > >> > >> -- > >> I hope that the information above helps you > >> > >> Good Luck > >> Jorge Silva > >> MCSA > >> Systems Administrator > >> > >> "Greg P" <gsp@newsgroups.nospam> wrote in message > >> news:D1DAA442-DF0E-42DC-9725-02A55AFEF4AB@microsoft.com... > >> > Each client machine is running Win XP Pro. > >> > > >> > No Proxy devices. > >> > > >> > I can access the internet from the server. > >> > > >> > Ipconfig on all 4 machines: > >> > > >> > Win 2003 Server > >> > > >> > Windows IP Configuration > >> > > >> > Host Name . . . . . . . . . . . . : Nugget > >> > Primary Dns Suffix . . . . . . . : sbs.net > >> > Node Type . . . . . . . . . . . . : Unknown > >> > IP Routing Enabled. . . . . . . . : Yes > >> > WINS Proxy Enabled. . . . . . . . : Yes > >> > DNS Suffix Search List. . . . . . : sbs.net > >> > austin.rr.com > >> > > >> > Ethernet adapter Local Area Connection: > >> > > >> > Connection-specific DNS Suffix . : austin.rr.com > >> > Description . . . . . . . . . . . : NVIDIA nForce Networking > >> > Controller > >> > Physical Address. . . . . . . . . : 00-XX-8D-DB-16-XX > >> > DHCP Enabled. . . . . . . . . . . : Yes > >> > Autoconfiguration Enabled . . . . : Yes > >> > IP Address. . . . . . . . . . . . : xxx.112.216.xxx > >> > Subnet Mask . . . . . . . . . . . : 255.255.240.0 > >> > Default Gateway . . . . . . . . . : 70.112.208.1 > >> > DHCP Server . . . . . . . . . . . : 10.37.160.1 > >> > DNS Servers . . . . . . . . . . . : 24.93.40.62 > >> > 24.93.40.63 > >> > 24.93.40.75 > >> > Lease Obtained. . . . . . . . . . : Thursday, June 08, 2006 11:20:40 > >> > AM > >> > Lease Expires . . . . . . . . . . : Thursday, June 08, 2006 1:20:40 > >> > PM > >> > > >> > Ethernet adapter Local Area Connection 2: > >> > > >> > Connection-specific DNS Suffix . : > >> > Description . . . . . . . . . . . : D-Link DFE-530TX+ PCI Fast > >> > Ethernet > >> > Adapt > >> > er (rev.F) > >> > Physical Address. . . . . . . . . : 00-xx-46-78-02-xx > >> > DHCP Enabled. . . . . . . . . . . : No > >> > IP Address. . . . . . . . . . . . : 192.168.10.1 > >> > Subnet Mask . . . . . . . . . . . : 255.255.255.0 > >> > Default Gateway . . . . . . . . . : > >> > DNS Servers . . . . . . . . . . . : 192.168.10.1 > >> > > >> > Laptop 1 > >> > > >> > Windows IP Configuration > >> > > >> > Host Name . . . . . . . . . . . . : Inspiron6000 > >> > Primary Dns Suffix . . . . . . . : sbs.net > >> > Node Type . . . . . . . . . . . . : Hybrid > >> > IP Routing Enabled. . . . . . . . : No > >> > WINS Proxy Enabled. . . . . . . . : No > >> > DNS Suffix Search List. . . . . . : sbs.net > >> > sbs.net > >> > sbs.net > >> > > >> > Ethernet adapter Local Area Connection: > >> > > >> > Connection-specific DNS Suffix . : sbs.net > >> > Description . . . . . . . . . . . : Broadcom 440x 10/100 > >> > Integrated > >> > Cont > >> > roller > >> > Physical Address. . . . . . . . . : 00-XX-43-79-BA-XX > >> > Dhcp Enabled. . . . . . . . . . . : Yes > >> > Autoconfiguration Enabled . . . . : Yes > >> > IP Address. . . . . . . . . . . . : 192.168.10.4 > >> > Subnet Mask . . . . . . . . . . . : 255.255.255.0 > >> > Default Gateway . . . . . . . . . : 192.168.10.1 > >> > DHCP Server . . . . . . . . . . . : 192.168.10.1 > >> > DNS Servers . . . . . . . . . . . : 192.168.10.1 > >> > Primary WINS Server . . . . . . . : 192.168.10.1 > >> > Lease Obtained. . . . . . . . . . : Thursday, June 08, 2006 > >> > 11:02:35 > >> > PM > >> > Lease Expires . . . . . . . . . . : Monday, January 18, 2038 > >> > 10:14:07 PM > >> > > >> > > >> > Ethernet adapter Wireless Network Connection: > >> > > >> > Connection-specific DNS Suffix . : sbs.net > >> > Description . . . . . . . . . . . : Intel(R) PRO/Wireless > >> > 2915ABG > >> > Networ > >> > k Connection > >> > Physical Address. . . . . . . . . : 00-12-F0-49-8B-CC > >> > Dhcp Enabled. . . . . . . . . . . : Yes > >> > Autoconfiguration Enabled . . . . : Yes > >> > IP Address. . . . . . . . . . . . : 192.168.10.5 > >> > Subnet Mask . . . . . . . . . . . : 255.255.255.0 > >> > Default Gateway . . . . . . . . . : 192.168.10.1 > >> > DHCP Server . . . . . . . . . . . : 192.168.10.1 > >> > DNS Servers . . . . . . . . . . . : 192.168.10.1 > >> > Primary WINS Server . . . . . . . : 192.168.10.1 > >> > Lease Obtained. . . . . . . . . . : Thursday, June 08, 2006 > >> > 9:19:27 > >> > PM > >> > Lease Expires . . . . . . . . . . : Monday, January 18, 2038 > >> > 10:14:07 PM > >> > > >> > > >> > Desktop 1 > >> > > >> > Windows IP Configuration > >> > > >> > Windows IP Configuration > >> > > >> > Host Name . . . . . . . . . . . . : GREGSDESKTOP > >> > Primary Dns Suffix . . . . . . . : sbs.net > >> > Node Type . . . . . . . . . . . . : Hybrid > >> > IP Routing Enabled. . . . . . . . : No > >> > WINS Proxy Enabled. . . . . . . . : No > >> > DNS Suffix Search List. . . . . . : sbs.net > >> > sbs.net > >> > > >> > Ethernet adapter Local Area Connection: > >> > > >> > Connection-specific DNS Suffix . : sbs.net > >> > Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network > >> > Connecti > >> > on > I uninstalled Norton totally from the desktop. If it can't connect to the It looks that your Dns resolution is working well. So the only explanation > internet I can't get a virus :) that I can remember at this moment is that there is something or some filter that prevents you from going to the internet. Check Internet options or any type of configuration internet related that you migh have in your pc. -- Show quoteHide quoteI hope that the information above helps you Good Luck Jorge Silva MCSA Systems Administrator "Greg P" <gsp@newsgroups.nospam> wrote in message news:3BDBCBA0-CDBF-4A47-8B91-B77978A81F49@microsoft.com... > Jorge, > > Unfortunately I'm in the same spot that I started in, except we solved the > file sharing issue on Laptop 2 by lowering the Norton firewall. I still > can't access the internet on the desktop or laptop 2, even though they are > on > the dame domain as Laptop 1 which can access the internet. With that > being > said I'm not sure if you still think this is a DNS problem? > >>Well you said that now you have everything working except Internet, and >>you also said that you don't have Proxy or any other thing that > prevents/restricts users to access to the internet, so you must have a DNS > resolution problem. > >>Do you have Forwarding enabled in the Dns server? > > Yes, this is set up with the correct ip addresses. > >>Test the resolution on the DC - Go to command prompt and type ping >>www.microsoft.com - check if returns the Ipaddress of the site > then go to the clients and check if the ping command returns the Ipaddress > of the site. > > All resolve the IP address, all requests time out. > >>Right click on it and choose properties then you should have the "File and >>Print Sharing for Microsoft Networks Selected"; however you should >>disable/deselect this on the Public Interface (Security purposes). > > The File and Print Sharing was selected previously. (there wasn't a > Public > Interface option for this nic, there are only 4 options in the properties > page, Client for MS Networks, Network Lad Balancing, File and Printer > Sharing, and TCP/IP) > >>Check also if is preventing Internet access or any other access to server >>or Dns, etc. Best practices here are for test DISABLE the Norton Firewall >>and test, in this way you can immediately check if this as relation with >>your current problems. > > I uninstalled Norton totally from the desktop. If it can't connect to the > internet I can't get a virus :) > > > "Jorge Silva" wrote: > >> In line >> >> >> >> > What is a multihomed DC? >> >> >> >> Is a Domain controller with more than one Nic (Network Interface Card) >> card >> >> >> >> > What do I need to change on my server to mave this work? >> >> >> >> Well you said that now you have everything working except Internet, and >> you >> also said that you don't have Proxy or any other thing that >> prevents/restricts users to access to the internet, so you must have a >> DNS >> resolution problem. >> >> >> >> - Do you have Forwarding enabled in the Dns server? If no go to the Dns >> console -> right click Dns server choose properties -> select forwarders >> tab -> Select All other Domains -> got to the Selected domain's forwarder >> Ipaddress list and place the ISP Dns server address -> click add -> >> restart >> Dns service. >> >> >> >> Test the resolution on the DC - Go to command prompt and type ping >> www.microsoft.com - check if returns the Ipaddress of the site, then go >> to >> the clients and check if the ping command returns the Ipaddress of the >> site. >> >> >> >> > Are you saying I shouldn't have WINS and DNS on the same computer? >> >> >> >> No. What I said was in a Multihomed DC you could have problems with Wins >> and >> Dns. >> >> >> > FYI I uninstalled WINS and see the same problem, do I need to remove >> > some >> > records somewhere? >> >> >> >> You'll only need WINS if you're using any APP in your network that needs >> NetBIOS resolution or if you have the need to browse over different >> subnets >> using for example Network Places. >> >> >> >> > As for configuring the DNS as you said I already had the interfaces set >> > to >> > only use the local Nic. >> >> >> >> - Great >> >> >> > As for setting the binding order the internal Nic was at the top of the >> > list. How do I check to see if file sharing is only on that NIC? >> >> >> >> - Right click on it and choose properties then you should have the "File >> and >> Print Sharing for Microsoft Networks Selected"; however you should >> disable/deselect this on the Public Interface (Security purposes). >> >> >> > I had lowered the windows firewall but there was a Norton Firewall that >> > was >> > preventing Laptop 2 from Filesharing. That now works. So both the >> > desktop >> > and Laptop 2 have the same issues. They get an IP, can perform >> > Fielsharing >> > but can't connect to the internet. >> >> >> >> Check also if is preventing Internet access or any other access to server >> or >> Dns, etc. Best practices here are for test DISABLE the Norton Firewall >> and >> test, in this way you can immediately check if this as relation with your >> current problems. >> >> >> >> -- >> I hope that the information above helps you >> >> Good Luck >> Jorge Silva >> MCSA >> Systems Administrator >> >> "Greg P" <gsp@newsgroups.nospam> wrote in message >> news:25530004-70F9-484D-A87A-26A6B823685F@microsoft.com... >> > Jorge, >> > >> > What is a multihomed DC? What do I need to change on my server to mave >> > this >> > work? Are you saying I shouldn't have WINS and DNS on the same >> > computer? >> > FYI I uninstalled WINS and see the same problem, do I need to remove >> > some >> > records somewhere? >> > >> > As for configuring the DNS as you said I already had the interfaces set >> > to >> > only use the local nic. >> > >> > As for setting the binding order the internal nic was at the top of the >> > list. How do I check to see if file sharing is only on that NIC? >> > >> > I had lowered the windows firewall but there was a Norton Firewall that >> > was >> > preventing Laptop 2 from Filesharing. That now works. So both the >> > desktop >> > and Laptop 2 have the same issues. They get an IP, can perform >> > Fielsharing >> > but can't connect to the internet. >> > >> > Thanks, >> > Greg >> > >> > "Jorge Silva" wrote: >> > >> >> >> >> - You shouldn't have a multihomed DC. >> >> check: >> >> >> >> Also, make sure the internal adapter is at the top of the binding >> >> order >> >> and >> >> that File Sharing is only bound on the internal adapter. >> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;266771 >> >> >> >> Active Directory communication fails on multihomed domain controllers >> >> >> >> http://support.microsoft.com/?id=272294 >> >> >> >> Name resolution and connectivity issues on a Routing and Remote Access >> >> Server that also runs DNS or WINS >> >> >> >> http://support.microsoft.com/kb/292822 >> >> >> >> >> >> - If the machines are running SP2 you need to open the FW to File >> >> share >> >> access. >> >> - Configure the Dns server to listen only on internal adpter (Open Dns >> >> server mmc console -> Right click on Dns server -> choose >> >> properties -> >> >> goto >> >> interfaces tab -> choose only the following IP Addresses, and make >> >> sure >> >> that >> >> you only have the internal interface there) >> >> >> >> >> >> -- >> >> I hope that the information above helps you >> >> >> >> Good Luck >> >> Jorge Silva >> >> MCSA >> >> Systems Administrator >> >> >> >> "Greg P" <gsp@newsgroups.nospam> wrote in message >> >> news:D1DAA442-DF0E-42DC-9725-02A55AFEF4AB@microsoft.com... >> >> > Each client machine is running Win XP Pro. >> >> > >> >> > No Proxy devices. >> >> > >> >> > I can access the internet from the server. >> >> > >> >> > Ipconfig on all 4 machines: >> >> > >> >> > Win 2003 Server >> >> > >> >> > Windows IP Configuration >> >> > >> >> > Host Name . . . . . . . . . . . . : Nugget >> >> > Primary Dns Suffix . . . . . . . : sbs.net >> >> > Node Type . . . . . . . . . . . . : Unknown >> >> > IP Routing Enabled. . . . . . . . : Yes >> >> > WINS Proxy Enabled. . . . . . . . : Yes >> >> > DNS Suffix Search List. . . . . . : sbs.net >> >> > austin.rr.com >> >> > >> >> > Ethernet adapter Local Area Connection: >> >> > >> >> > Connection-specific DNS Suffix . : austin.rr.com >> >> > Description . . . . . . . . . . . : NVIDIA nForce Networking >> >> > Controller >> >> > Physical Address. . . . . . . . . : 00-XX-8D-DB-16-XX >> >> > DHCP Enabled. . . . . . . . . . . : Yes >> >> > Autoconfiguration Enabled . . . . : Yes >> >> > IP Address. . . . . . . . . . . . : xxx.112.216.xxx >> >> > Subnet Mask . . . . . . . . . . . : 255.255.240.0 >> >> > Default Gateway . . . . . . . . . : 70.112.208.1 >> >> > DHCP Server . . . . . . . . . . . : 10.37.160.1 >> >> > DNS Servers . . . . . . . . . . . : 24.93.40.62 >> >> > 24.93.40.63 >> >> > 24.93.40.75 >> >> > Lease Obtained. . . . . . . . . . : Thursday, June 08, 2006 >> >> > 11:20:40 >> >> > AM >> >> > Lease Expires . . . . . . . . . . : Thursday, June 08, 2006 >> >> > 1:20:40 >> >> > PM >> >> > >> >> > Ethernet adapter Local Area Connection 2: >> >> > >> >> > Connection-specific DNS Suffix . : >> >> > Description . . . . . . . . . . . : D-Link DFE-530TX+ PCI Fast >> >> > Ethernet >> >> > Adapt >> >> > er (rev.F) >> >> > Physical Address. . . . . . . . . : 00-xx-46-78-02-xx >> >> > DHCP Enabled. . . . . . . . . . . : No >> >> > IP Address. . . . . . . . . . . . : 192.168.10.1 >> >> > Subnet Mask . . . . . . . . . . . : 255.255.255.0 >> >> > Default Gateway . . . . . . . . . : >> >> > DNS Servers . . . . . . . . . . . : 192.168.10.1 >> >> > >> >> > Laptop 1 >> >> > >> >> > Windows IP Configuration >> >> > >> >> > Host Name . . . . . . . . . . . . : Inspiron6000 >> >> > Primary Dns Suffix . . . . . . . : sbs.net >> >> > Node Type . . . . . . . . . . . . : Hybrid >> >> > IP Routing Enabled. . . . . . . . : No >> >> > WINS Proxy Enabled. . . . . . . . : No >> >> > DNS Suffix Search List. . . . . . : sbs.net >> >> > sbs.net >> >> > sbs.net >> >> > >> >> > Ethernet adapter Local Area Connection: >> >> > >> >> > Connection-specific DNS Suffix . : sbs.net >> >> > Description . . . . . . . . . . . : Broadcom 440x 10/100 >> >> > Integrated >> >> > Cont >> >> > roller >> >> > Physical Address. . . . . . . . . : 00-XX-43-79-BA-XX >> >> > Dhcp Enabled. . . . . . . . . . . : Yes >> >> > Autoconfiguration Enabled . . . . : Yes >> >> > IP Address. . . . . . . . . . . . : 192.168.10.4 >> >> > Subnet Mask . . . . . . . . . . . : 255.255.255.0 >> >> > Default Gateway . . . . . . . . . : 192.168.10.1 >> >> > DHCP Server . . . . . . . . . . . : 192.168.10.1 >> >> > DNS Servers . . . . . . . . . . . : 192.168.10.1 >> >> > Primary WINS Server . . . . . . . : 192.168.10.1 >> >> > Lease Obtained. . . . . . . . . . : Thursday, June 08, 2006 >> >> > 11:02:35 >> >> > PM >> >> > Lease Expires . . . . . . . . . . : Monday, January 18, 2038 >> >> > 10:14:07 PM >> >> > >> >> > >> >> > Ethernet adapter Wireless Network Connection: >> >> > >> >> > Connection-specific DNS Suffix . : sbs.net >> >> > Description . . . . . . . . . . . : Intel(R) PRO/Wireless >> >> > 2915ABG >> >> > Networ >> >> > k Connection >> >> > Physical Address. . . . . . . . . : 00-12-F0-49-8B-CC >> >> > Dhcp Enabled. . . . . . . . . . . : Yes >> >> > Autoconfiguration Enabled . . . . : Yes >> >> > IP Address. . . . . . . . . . . . : 192.168.10.5 >> >> > Subnet Mask . . . . . . . . . . . : 255.255.255.0 >> >> > Default Gateway . . . . . . . . . : 192.168.10.1 >> >> > DHCP Server . . . . . . . . . . . : 192.168.10.1 >> >> > DNS Servers . . . . . . . . . . . : 192.168.10.1 >> >> > Primary WINS Server . . . . . . . : 192.168.10.1 >> >> > Lease Obtained. . . . . . . . . . : Thursday, June 08, 2006 >> >> > 9:19:27 >> >> > PM >> >> > Lease Expires . . . . . . . . . . : Monday, January 18, 2038 >> >> > 10:14:07 PM >> >> > >> >> > >> >> > Desktop 1 >> >> > >> >> > Windows IP Configuration >> >> > >> >> > Windows IP Configuration >> >> > >> >> > Host Name . . . . . . . . . . . . : GREGSDESKTOP >> >> > Primary Dns Suffix . . . . . . . : sbs.net >> >> > Node Type . . . . . . . . . . . . : Hybrid >> >> > IP Routing Enabled. . . . . . . . : No >> >> > WINS Proxy Enabled. . . . . . . . : No >> >> > DNS Suffix Search List. . . . . . : sbs.net >> >> > sbs.net >> >> > >> >> > Ethernet adapter Local Area Connection: >> >> > >> >> > Connection-specific DNS Suffix . : sbs.net >> >> > Description . . . . . . . . . . . : Intel(R) PRO/100 VE >> >> > Network >> >> > Connecti >> >> > on Jorge,
I reset internet options to no avail. One thing i'm not sure about is when I ping the internet from any computer on the network the request times out. Even the server and the laptop that the internet works on. Otherwise I'm totally stumped. Thanks, Greg Show quoteHide quote "Jorge Silva" wrote: > > I uninstalled Norton totally from the desktop. If it can't connect to the > > internet I can't get a virus :) > > It looks that your Dns resolution is working well. So the only explanation > that I can remember at this moment is that there is something or some filter > that prevents you from going to the internet. Check Internet options or any > type of configuration internet related that you migh have in your pc. > -- > I hope that the information above helps you > > Good Luck > Jorge Silva > MCSA > Systems Administrator > > "Greg P" <gsp@newsgroups.nospam> wrote in message > news:3BDBCBA0-CDBF-4A47-8B91-B77978A81F49@microsoft.com... > > Jorge, > > > > Unfortunately I'm in the same spot that I started in, except we solved the > > file sharing issue on Laptop 2 by lowering the Norton firewall. I still > > can't access the internet on the desktop or laptop 2, even though they are > > on > > the dame domain as Laptop 1 which can access the internet. With that > > being > > said I'm not sure if you still think this is a DNS problem? > > > >>Well you said that now you have everything working except Internet, and > >>you also said that you don't have Proxy or any other thing that > > prevents/restricts users to access to the internet, so you must have a DNS > > resolution problem. > > > >>Do you have Forwarding enabled in the Dns server? > > > > Yes, this is set up with the correct ip addresses. > > > >>Test the resolution on the DC - Go to command prompt and type ping > >>www.microsoft.com - check if returns the Ipaddress of the site > > then go to the clients and check if the ping command returns the Ipaddress > > of the site. > > > > All resolve the IP address, all requests time out. > > > >>Right click on it and choose properties then you should have the "File and > >>Print Sharing for Microsoft Networks Selected"; however you should > >>disable/deselect this on the Public Interface (Security purposes). > > > > The File and Print Sharing was selected previously. (there wasn't a > > Public > > Interface option for this nic, there are only 4 options in the properties > > page, Client for MS Networks, Network Lad Balancing, File and Printer > > Sharing, and TCP/IP) > > > >>Check also if is preventing Internet access or any other access to server > >>or Dns, etc. Best practices here are for test DISABLE the Norton Firewall > >>and test, in this way you can immediately check if this as relation with > >>your current problems. > > > > I uninstalled Norton totally from the desktop. If it can't connect to the > > internet I can't get a virus :) > > > > > > "Jorge Silva" wrote: > > > >> In line > >> > >> > >> > >> > What is a multihomed DC? > >> > >> > >> > >> Is a Domain controller with more than one Nic (Network Interface Card) > >> card > >> > >> > >> > >> > What do I need to change on my server to mave this work? > >> > >> > >> > >> Well you said that now you have everything working except Internet, and > >> you > >> also said that you don't have Proxy or any other thing that > >> prevents/restricts users to access to the internet, so you must have a > >> DNS > >> resolution problem. > >> > >> > >> > >> - Do you have Forwarding enabled in the Dns server? If no go to the Dns > >> console -> right click Dns server choose properties -> select forwarders > >> tab -> Select All other Domains -> got to the Selected domain's forwarder > >> Ipaddress list and place the ISP Dns server address -> click add -> > >> restart > >> Dns service. > >> > >> > >> > >> Test the resolution on the DC - Go to command prompt and type ping > >> www.microsoft.com - check if returns the Ipaddress of the site, then go > >> to > >> the clients and check if the ping command returns the Ipaddress of the > >> site. > >> > >> > >> > >> > Are you saying I shouldn't have WINS and DNS on the same computer? > >> > >> > >> > >> No. What I said was in a Multihomed DC you could have problems with Wins > >> and > >> Dns. > >> > >> > >> > FYI I uninstalled WINS and see the same problem, do I need to remove > >> > some > >> > records somewhere? > >> > >> > >> > >> You'll only need WINS if you're using any APP in your network that needs > >> NetBIOS resolution or if you have the need to browse over different > >> subnets > >> using for example Network Places. > >> > >> > >> > >> > As for configuring the DNS as you said I already had the interfaces set > >> > to > >> > only use the local Nic. > >> > >> > >> > >> - Great > >> > >> > >> > As for setting the binding order the internal Nic was at the top of the > >> > list. How do I check to see if file sharing is only on that NIC? > >> > >> > >> > >> - Right click on it and choose properties then you should have the "File > >> and > >> Print Sharing for Microsoft Networks Selected"; however you should > >> disable/deselect this on the Public Interface (Security purposes). > >> > >> > >> > I had lowered the windows firewall but there was a Norton Firewall that > >> > was > >> > preventing Laptop 2 from Filesharing. That now works. So both the > >> > desktop > >> > and Laptop 2 have the same issues. They get an IP, can perform > >> > Fielsharing > >> > but can't connect to the internet. > >> > >> > >> > >> Check also if is preventing Internet access or any other access to server > >> or > >> Dns, etc. Best practices here are for test DISABLE the Norton Firewall > >> and > >> test, in this way you can immediately check if this as relation with your > >> current problems. > >> > >> > >> > >> -- > >> I hope that the information above helps you > >> > >> Good Luck > >> Jorge Silva > >> MCSA > >> Systems Administrator > >> > >> "Greg P" <gsp@newsgroups.nospam> wrote in message > >> news:25530004-70F9-484D-A87A-26A6B823685F@microsoft.com... > >> > Jorge, > >> > > >> > What is a multihomed DC? What do I need to change on my server to mave > >> > this > >> > work? Are you saying I shouldn't have WINS and DNS on the same > >> > computer? > >> > FYI I uninstalled WINS and see the same problem, do I need to remove > >> > some > >> > records somewhere? > >> > > >> > As for configuring the DNS as you said I already had the interfaces set > >> > to > >> > only use the local nic. > >> > > >> > As for setting the binding order the internal nic was at the top of the > >> > list. How do I check to see if file sharing is only on that NIC? > >> > > >> > I had lowered the windows firewall but there was a Norton Firewall that > >> > was > >> > preventing Laptop 2 from Filesharing. That now works. So both the > >> > desktop > >> > and Laptop 2 have the same issues. They get an IP, can perform > >> > Fielsharing > >> > but can't connect to the internet. > >> > > >> > Thanks, > >> > Greg > >> > > >> > "Jorge Silva" wrote: > >> > > >> >> > >> >> - You shouldn't have a multihomed DC. > >> >> check: > >> >> > >> >> Also, make sure the internal adapter is at the top of the binding > >> >> order > >> >> and > >> >> that File Sharing is only bound on the internal adapter. > >> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;266771 > >> >> > >> >> Active Directory communication fails on multihomed domain controllers > >> >> > >> >> http://support.microsoft.com/?id=272294 > >> >> > >> >> Name resolution and connectivity issues on a Routing and Remote Access > >> >> Server that also runs DNS or WINS > >> >> > >> >> http://support.microsoft.com/kb/292822 > >> >> > >> >> > >> >> - If the machines are running SP2 you need to open the FW to File > >> >> share > >> >> access. > >> >> - Configure the Dns server to listen only on internal adpter (Open Dns > >> >> server mmc console -> Right click on Dns server -> choose > >> >> properties -> > >> >> goto > >> >> interfaces tab -> choose only the following IP Addresses, and make > >> >> sure > >> >> that > >> >> you only have the internal interface there) > >> >> > >> >> > >> >> -- > >> >> I hope that the information above helps you > >> >> > >> >> Good Luck > >> >> Jorge Silva > >> >> MCSA > >> >> Systems Administrator > >> >> > >> >> "Greg P" <gsp@newsgroups.nospam> wrote in message > >> >> news:D1DAA442-DF0E-42DC-9725-02A55AFEF4AB@microsoft.com... > >> >> > Each client machine is running Win XP Pro. > >> >> > > >> >> > No Proxy devices. > >> >> > > >> >> > I can access the internet from the server. > >> >> > > >> >> > Ipconfig on all 4 machines: > >> >> > > >> >> > Win 2003 Server > >> >> > > >> >> > Windows IP Configuration > >> >> > > >> >> > Host Name . . . . . . . . . . . . : Nugget > >> >> > Primary Dns Suffix . . . . . . . : sbs.net > >> >> > Node Type . . . . . . . . . . . . : Unknown > >> >> > IP Routing Enabled. . . . . . . . : Yes > >> >> > WINS Proxy Enabled. . . . . . . . : Yes > >> >> > DNS Suffix Search List. . . . . . : sbs.net > >> >> > austin.rr.com > >> >> > > >> >> > Ethernet adapter Local Area Connection: > >> >> > > >> >> > Connection-specific DNS Suffix . : austin.rr.com > >> >> > Description . . . . . . . . . . . : NVIDIA nForce Networking > >> >> > Controller > >> >> > Physical Address. . . . . . . . . : 00-XX-8D-DB-16-XX > >> >> > DHCP Enabled. . . . . . . . . . . : Yes > >> >> > Autoconfiguration Enabled . . . . : Yes > >> >> > IP Address. . . . . . . . . . . . : xxx.112.216.xxx > >> >> > Subnet Mask . . . . . . . . . . . : 255.255.240.0 > >> >> > Default Gateway . . . . . . . . . : 70.112.208.1 > >> >> > DHCP Server . . . . . . . . . . . : 10.37.160.1 > >> >> > DNS Servers . . . . . . . . . . . : 24.93.40.62 > >> >> > 24.93.40.63 > >> >> > 24.93.40.75 > >> >> > Lease Obtained. . . . . . . . . . : Thursday, June 08, 2006 > >> >> > 11:20:40 > >> >> > AM > >> >> > Lease Expires . . . . . . . . . . : Thursday, June 08, 2006 > >> >> > 1:20:40 > >> >> > PM > >> >> > > >> >> > Ethernet adapter Local Area Connection 2: > >> >> > > >> >> > Connection-specific DNS Suffix . : > >> >> > Description . . . . . . . . . . . : D-Link DFE-530TX+ PCI Fast > >> >> > Ethernet > >> >> > Adapt > >> >> > er (rev.F) The request TimesOut -> normal, the servers in the internet won't reply to
ping requets because they are protected by firewalls. Basic Steps to troubleshoot are: 1. Ping the loopback address to verify that TCP/IP is installed and configured correctly on the local computer. To perform this step, enter ping 127.0.0.1 at a command prompt. If the loopback step fails, the IP stack is not responding. This problem might be occurring because the TCP drivers are corrupted, the network adapter might not be working, or another service might be interfering with IP. 2. Ping the IP address of the local computer to verify that an address has been added correctly. To perform this step, enter ping <IP address of local host> at a command prompt. 3. Ping the IP address of the default gateway. This step verifies that the default gateway is reachable and that the local host can communicate with another host on the network. To perform this step, enter ping <IP address of default gateway> at a command prompt. Then you can use Tracert which is a route-tracing utility that allows you to track the path of a forwarded packet from router to router for up to 30 hops. Tracert works by sending ICMP echo requests to an IP address, while incrementing the Time to Live (TTL) field in the IP header, starting at 1, and analyzing the ICMP errors that are returned. Tracert prints out an ordered list of the routers in the path that returned these error messages. Type on command prompt: <tracert www.microsoft.com> press enter -- Show quoteHide quoteI hope that the information above helps you Good Luck Jorge Silva MCSA Systems Administrator "Greg P" <gsp@newsgroups.nospam> wrote in message news:01B390CF-90D6-4305-9008-8E34BE2E69E6@microsoft.com... > Jorge, > > I reset internet options to no avail. One thing i'm not sure about is > when > I ping the internet from any computer on the network the request times > out. > Even the server and the laptop that the internet works on. Otherwise I'm > totally stumped. > > Thanks, > Greg > > "Jorge Silva" wrote: > >> > I uninstalled Norton totally from the desktop. If it can't connect to >> > the >> > internet I can't get a virus :) >> >> It looks that your Dns resolution is working well. So the only >> explanation >> that I can remember at this moment is that there is something or some >> filter >> that prevents you from going to the internet. Check Internet options or >> any >> type of configuration internet related that you migh have in your pc. >> -- >> I hope that the information above helps you >> >> Good Luck >> Jorge Silva >> MCSA >> Systems Administrator >> >> "Greg P" <gsp@newsgroups.nospam> wrote in message >> news:3BDBCBA0-CDBF-4A47-8B91-B77978A81F49@microsoft.com... >> > Jorge, >> > >> > Unfortunately I'm in the same spot that I started in, except we solved >> > the >> > file sharing issue on Laptop 2 by lowering the Norton firewall. I >> > still >> > can't access the internet on the desktop or laptop 2, even though they >> > are >> > on >> > the dame domain as Laptop 1 which can access the internet. With that >> > being >> > said I'm not sure if you still think this is a DNS problem? >> > >> >>Well you said that now you have everything working except Internet, and >> >>you also said that you don't have Proxy or any other thing that >> > prevents/restricts users to access to the internet, so you must have a >> > DNS >> > resolution problem. >> > >> >>Do you have Forwarding enabled in the Dns server? >> > >> > Yes, this is set up with the correct ip addresses. >> > >> >>Test the resolution on the DC - Go to command prompt and type ping >> >>www.microsoft.com - check if returns the Ipaddress of the site >> > then go to the clients and check if the ping command returns the >> > Ipaddress >> > of the site. >> > >> > All resolve the IP address, all requests time out. >> > >> >>Right click on it and choose properties then you should have the "File >> >>and >> >>Print Sharing for Microsoft Networks Selected"; however you should >> >>disable/deselect this on the Public Interface (Security purposes). >> > >> > The File and Print Sharing was selected previously. (there wasn't a >> > Public >> > Interface option for this nic, there are only 4 options in the >> > properties >> > page, Client for MS Networks, Network Lad Balancing, File and Printer >> > Sharing, and TCP/IP) >> > >> >>Check also if is preventing Internet access or any other access to >> >>server >> >>or Dns, etc. Best practices here are for test DISABLE the Norton >> >>Firewall >> >>and test, in this way you can immediately check if this as relation >> >>with >> >>your current problems. >> > >> > I uninstalled Norton totally from the desktop. If it can't connect to >> > the >> > internet I can't get a virus :) >> > >> > >> > "Jorge Silva" wrote: >> > >> >> In line >> >> >> >> >> >> >> >> > What is a multihomed DC? >> >> >> >> >> >> >> >> Is a Domain controller with more than one Nic (Network Interface Card) >> >> card >> >> >> >> >> >> >> >> > What do I need to change on my server to mave this work? >> >> >> >> >> >> >> >> Well you said that now you have everything working except Internet, >> >> and >> >> you >> >> also said that you don't have Proxy or any other thing that >> >> prevents/restricts users to access to the internet, so you must have a >> >> DNS >> >> resolution problem. >> >> >> >> >> >> >> >> - Do you have Forwarding enabled in the Dns server? If no go to the >> >> Dns >> >> console -> right click Dns server choose properties -> select >> >> forwarders >> >> tab -> Select All other Domains -> got to the Selected domain's >> >> forwarder >> >> Ipaddress list and place the ISP Dns server address -> click add -> >> >> restart >> >> Dns service. >> >> >> >> >> >> >> >> Test the resolution on the DC - Go to command prompt and type ping >> >> www.microsoft.com - check if returns the Ipaddress of the site, then >> >> go >> >> to >> >> the clients and check if the ping command returns the Ipaddress of the >> >> site. >> >> >> >> >> >> >> >> > Are you saying I shouldn't have WINS and DNS on the same computer? >> >> >> >> >> >> >> >> No. What I said was in a Multihomed DC you could have problems with >> >> Wins >> >> and >> >> Dns. >> >> >> >> >> >> > FYI I uninstalled WINS and see the same problem, do I need to >> >> > remove >> >> > some >> >> > records somewhere? >> >> >> >> >> >> >> >> You'll only need WINS if you're using any APP in your network that >> >> needs >> >> NetBIOS resolution or if you have the need to browse over different >> >> subnets >> >> using for example Network Places. >> >> >> >> >> >> >> >> > As for configuring the DNS as you said I already had the interfaces >> >> > set >> >> > to >> >> > only use the local Nic. >> >> >> >> >> >> >> >> - Great >> >> >> >> >> >> > As for setting the binding order the internal Nic was at the top of >> >> > the >> >> > list. How do I check to see if file sharing is only on that NIC? >> >> >> >> >> >> >> >> - Right click on it and choose properties then you should have the >> >> "File >> >> and >> >> Print Sharing for Microsoft Networks Selected"; however you should >> >> disable/deselect this on the Public Interface (Security purposes). >> >> >> >> >> >> > I had lowered the windows firewall but there was a Norton Firewall >> >> > that >> >> > was >> >> > preventing Laptop 2 from Filesharing. That now works. So both the >> >> > desktop >> >> > and Laptop 2 have the same issues. They get an IP, can perform >> >> > Fielsharing >> >> > but can't connect to the internet. >> >> >> >> >> >> >> >> Check also if is preventing Internet access or any other access to >> >> server >> >> or >> >> Dns, etc. Best practices here are for test DISABLE the Norton Firewall >> >> and >> >> test, in this way you can immediately check if this as relation with >> >> your >> >> current problems. >> >> >> >> >> >> >> >> -- >> >> I hope that the information above helps you >> >> >> >> Good Luck >> >> Jorge Silva >> >> MCSA >> >> Systems Administrator >> >> >> >> "Greg P" <gsp@newsgroups.nospam> wrote in message >> >> news:25530004-70F9-484D-A87A-26A6B823685F@microsoft.com... >> >> > Jorge, >> >> > >> >> > What is a multihomed DC? What do I need to change on my server to >> >> > mave >> >> > this >> >> > work? Are you saying I shouldn't have WINS and DNS on the same >> >> > computer? >> >> > FYI I uninstalled WINS and see the same problem, do I need to >> >> > remove >> >> > some >> >> > records somewhere? >> >> > >> >> > As for configuring the DNS as you said I already had the interfaces >> >> > set >> >> > to >> >> > only use the local nic. >> >> > >> >> > As for setting the binding order the internal nic was at the top of >> >> > the >> >> > list. How do I check to see if file sharing is only on that NIC? >> >> > >> >> > I had lowered the windows firewall but there was a Norton Firewall >> >> > that >> >> > was >> >> > preventing Laptop 2 from Filesharing. That now works. So both the >> >> > desktop >> >> > and Laptop 2 have the same issues. They get an IP, can perform >> >> > Fielsharing >> >> > but can't connect to the internet. >> >> > >> >> > Thanks, >> >> > Greg >> >> > >> >> > "Jorge Silva" wrote: >> >> > >> >> >> >> >> >> - You shouldn't have a multihomed DC. >> >> >> check: >> >> >> >> >> >> Also, make sure the internal adapter is at the top of the binding >> >> >> order >> >> >> and >> >> >> that File Sharing is only bound on the internal adapter. >> >> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;266771 >> >> >> >> >> >> Active Directory communication fails on multihomed domain >> >> >> controllers >> >> >> >> >> >> http://support.microsoft.com/?id=272294 >> >> >> >> >> >> Name resolution and connectivity issues on a Routing and Remote >> >> >> Access >> >> >> Server that also runs DNS or WINS >> >> >> >> >> >> http://support.microsoft.com/kb/292822 >> >> >> >> >> >> >> >> >> - If the machines are running SP2 you need to open the FW to File >> >> >> share >> >> >> access. >> >> >> - Configure the Dns server to listen only on internal adpter (Open >> >> >> Dns >> >> >> server mmc console -> Right click on Dns server -> choose >> >> >> properties -> >> >> >> goto >> >> >> interfaces tab -> choose only the following IP Addresses, and make >> >> >> sure >> >> >> that >> >> >> you only have the internal interface there) >> >> >> >> >> >> >> >> >> -- >> >> >> I hope that the information above helps you >> >> >> >> >> >> Good Luck >> >> >> Jorge Silva >> >> >> MCSA >> >> >> Systems Administrator >> >> >> >> >> >> "Greg P" <gsp@newsgroups.nospam> wrote in message >> >> >> news:D1DAA442-DF0E-42DC-9725-02A55AFEF4AB@microsoft.com... >> >> >> > Each client machine is running Win XP Pro. >> >> >> > >> >> >> > No Proxy devices. >> >> >> > >> >> >> > I can access the internet from the server. >> >> >> > >> >> >> > Ipconfig on all 4 machines: >> >> >> > >> >> >> > Win 2003 Server >> >> >> > >> >> >> > Windows IP Configuration >> >> >> > >> >> >> > Host Name . . . . . . . . . . . . : Nugget >> >> >> > Primary Dns Suffix . . . . . . . : sbs.net >> >> >> > Node Type . . . . . . . . . . . . : Unknown >> >> >> > IP Routing Enabled. . . . . . . . : Yes >> >> >> > WINS Proxy Enabled. . . . . . . . : Yes >> >> >> > DNS Suffix Search List. . . . . . : sbs.net >> >> >> > austin.rr.com >> >> >> > >> >> >> > Ethernet adapter Local Area Connection: >> >> >> > >> >> >> > Connection-specific DNS Suffix . : austin.rr.com >> >> >> > Description . . . . . . . . . . . : NVIDIA nForce Networking >> >> >> > Controller >> >> >> > Physical Address. . . . . . . . . : 00-XX-8D-DB-16-XX >> >> >> > DHCP Enabled. . . . . . . . . . . : Yes >> >> >> > Autoconfiguration Enabled . . . . : Yes >> >> >> > IP Address. . . . . . . . . . . . : xxx.112.216.xxx >> >> >> > Subnet Mask . . . . . . . . . . . : 255.255.240.0 >> >> >> > Default Gateway . . . . . . . . . : 70.112.208.1 >> >> >> > DHCP Server . . . . . . . . . . . : 10.37.160.1 >> >> >> > DNS Servers . . . . . . . . . . . : 24.93.40.62 >> >> >> > 24.93.40.63 >> >> >> > 24.93.40.75 >> >> >> > Lease Obtained. . . . . . . . . . : Thursday, June 08, 2006 >> >> >> > 11:20:40 >> >> >> > AM >> >> >> > Lease Expires . . . . . . . . . . : Thursday, June 08, 2006 >> >> >> > 1:20:40 >> >> >> > PM >> >> >> > >> >> >> > Ethernet adapter Local Area Connection 2: >> >> >> > >> >> >> > Connection-specific DNS Suffix . : >> >> >> > Description . . . . . . . . . . . : D-Link DFE-530TX+ PCI Fast >> >> >> > Ethernet >> >> >> > Adapt >> >> >> > er (rev.F) Yes I am using Remote Access to access the internet. All of your suggustions
worked (got a responce) and my trace gets out to MSN, but internet still doesn't work. 192..168.10.1 is my server 192.168.10.3 is my desktop (the one I ran the trace on, but can't use the internet on) below are my pings and trace. Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\gperrego>ping 127.0.0.1 Pinging 127.0.0.1 with 32 bytes of data: Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Ping statistics for 127.0.0.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\Documents and Settings\gperrego>ping 192.168.10.1 Pinging 192.168.10.1 with 32 bytes of data: Reply from 192.168.10.1: bytes=32 time=101ms TTL=128 Reply from 192.168.10.1: bytes=32 time=174ms TTL=128 Reply from 192.168.10.1: bytes=32 time=1ms TTL=128 Reply from 192.168.10.1: bytes=32 time=1ms TTL=128 Ping statistics for 192.168.10.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 174ms, Average = 69ms C:\Documents and Settings\gperrego>ping 192.168.10.3 Pinging 192.168.10.3 with 32 bytes of data: Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 Ping statistics for 192.168.10.3: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\Documents and Settings\gperrego>ping 192.168.10.2 Pinging 192.168.10.2 with 32 bytes of data: Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 Ping statistics for 192.168.10.2: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\Documents and Settings\gperrego>tracert www.microsoft.com Tracing route to lb1.www.ms.akadns.net [207.46.199.30] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms nugget.sbs.net [192.168.10.1] 2 7 ms 8 ms 8 ms 10.37.160.1 3 8 ms 8 ms 8 ms gig0-2.austtxa-ubr7.austin.rr.com [24.27.12.81] 4 9 ms 9 ms 7 ms gig2-3.austtxa-rtr1.austin.rr.com [24.27.12.85] 5 18 ms 10 ms 9 ms srp0-0.austtxrdc-rtr2.austin.rr.com [24.27.12.34 ] 6 9 ms 8 ms 9 ms pos1-0.austtxrdc-rtr4.texas.rr.com [66.68.1.110] 7 17 ms 18 ms 16 ms son0-0-0.hstqtxl3-rtr1.texas.rr.com [24.93.33.15 3] 8 18 ms 17 ms 16 ms 4.79.88.21 9 16 ms 16 ms 18 ms ge-2-0-0.mp1.Houston1.Level3.net [4.68.97.241] 10 172 ms 110 ms 60 ms as-1-0.mp2.Seattle1.Level3.net [209.247.10.133] 11 61 ms 61 ms 59 ms ge-2-0-0-52.gar1.Seattle1.Level3.net [4.68.105.4 1] 12 60 ms 61 ms 62 ms 65.59.235.6 13 94 ms 62 ms 62 ms 207.46.37.225 14 62 ms 61 ms 63 ms pos1-0.tuk-12ix-1b.ntwk.msn.net [207.46.36.146] 15 60 ms 62 ms 62 ms pos1-0.tke-12ix-1b.ntwk.msn.net [207.46.155.5] 16 60 ms 60 ms 60 ms po10.tuk-65ns-mcs-1a.ntwk.msn.net [207.46.224.15 1] 17 * ^C C:\Documents and Settings\gperrego> Show quoteHide quote "Jorge Silva" wrote: > The request TimesOut -> normal, the servers in the internet won't reply to > ping requets because they are protected by firewalls. > > Basic Steps to troubleshoot are: > > 1. Ping the loopback address to verify that TCP/IP is installed and > configured correctly on the local computer. To perform this step, enter ping > 127.0.0.1 at a command prompt. > > If the loopback step fails, the IP stack is not responding. This problem > might be occurring because the TCP drivers are corrupted, the network > adapter might not be working, or another service might be interfering with > IP. > > > > 2. Ping the IP address of the local computer to verify that an address has > been added correctly. To perform this step, enter ping <IP address of local > host> at a command prompt. > > > > 3. Ping the IP address of the default gateway. This step verifies that the > default gateway is reachable and that the local host can communicate with > another host on the network. To perform this step, enter ping <IP address of > default gateway> at a command prompt. > > > > Then you can use Tracert which is a route-tracing utility that allows you to > track the path of a forwarded packet from router to router for up to 30 > hops. Tracert works by sending ICMP echo requests to an IP address, while > incrementing the Time to Live (TTL) field in the IP header, starting at 1, > and analyzing the ICMP errors that are returned. Tracert prints out an > ordered list of the routers in the path that returned these error messages. > > > Type on command prompt: > <tracert www.microsoft.com> press enter > > > -- > I hope that the information above helps you > > Good Luck > Jorge Silva > MCSA > Systems Administrator > > "Greg P" <gsp@newsgroups.nospam> wrote in message > news:01B390CF-90D6-4305-9008-8E34BE2E69E6@microsoft.com... > > Jorge, > > > > I reset internet options to no avail. One thing i'm not sure about is > > when > > I ping the internet from any computer on the network the request times > > out. > > Even the server and the laptop that the internet works on. Otherwise I'm > > totally stumped. > > > > Thanks, > > Greg > > > > "Jorge Silva" wrote: > > > >> > I uninstalled Norton totally from the desktop. If it can't connect to > >> > the > >> > internet I can't get a virus :) > >> > >> It looks that your Dns resolution is working well. So the only > >> explanation > >> that I can remember at this moment is that there is something or some > >> filter > >> that prevents you from going to the internet. Check Internet options or > >> any > >> type of configuration internet related that you migh have in your pc. > >> -- > >> I hope that the information above helps you > >> > >> Good Luck > >> Jorge Silva > >> MCSA > >> Systems Administrator > >> > >> "Greg P" <gsp@newsgroups.nospam> wrote in message > >> news:3BDBCBA0-CDBF-4A47-8B91-B77978A81F49@microsoft.com... > >> > Jorge, > >> > > >> > Unfortunately I'm in the same spot that I started in, except we solved > >> > the > >> > file sharing issue on Laptop 2 by lowering the Norton firewall. I > >> > still > >> > can't access the internet on the desktop or laptop 2, even though they > >> > are > >> > on > >> > the dame domain as Laptop 1 which can access the internet. With that > >> > being > >> > said I'm not sure if you still think this is a DNS problem? > >> > > >> >>Well you said that now you have everything working except Internet, and > >> >>you also said that you don't have Proxy or any other thing that > >> > prevents/restricts users to access to the internet, so you must have a > >> > DNS > >> > resolution problem. > >> > > >> >>Do you have Forwarding enabled in the Dns server? > >> > > >> > Yes, this is set up with the correct ip addresses. > >> > > >> >>Test the resolution on the DC - Go to command prompt and type ping > >> >>www.microsoft.com - check if returns the Ipaddress of the site > >> > then go to the clients and check if the ping command returns the > >> > Ipaddress > >> > of the site. > >> > > >> > All resolve the IP address, all requests time out. > >> > > >> >>Right click on it and choose properties then you should have the "File > >> >>and > >> >>Print Sharing for Microsoft Networks Selected"; however you should > >> >>disable/deselect this on the Public Interface (Security purposes). > >> > > >> > The File and Print Sharing was selected previously. (there wasn't a > >> > Public > >> > Interface option for this nic, there are only 4 options in the > >> > properties > >> > page, Client for MS Networks, Network Lad Balancing, File and Printer > >> > Sharing, and TCP/IP) > >> > > >> >>Check also if is preventing Internet access or any other access to > >> >>server > >> >>or Dns, etc. Best practices here are for test DISABLE the Norton > >> >>Firewall > >> >>and test, in this way you can immediately check if this as relation > >> >>with > >> >>your current problems. > >> > > >> > I uninstalled Norton totally from the desktop. If it can't connect to > >> > the > >> > internet I can't get a virus :) > >> > > >> > > >> > "Jorge Silva" wrote: > >> > > >> >> In line > >> >> > >> >> > >> >> > >> >> > What is a multihomed DC? > >> >> > >> >> > >> >> > >> >> Is a Domain controller with more than one Nic (Network Interface Card) > >> >> card > >> >> > >> >> > >> >> > >> >> > What do I need to change on my server to mave this work? > >> >> > >> >> > >> >> > >> >> Well you said that now you have everything working except Internet, > >> >> and > >> >> you > >> >> also said that you don't have Proxy or any other thing that > >> >> prevents/restricts users to access to the internet, so you must have a > >> >> DNS > >> >> resolution problem. > >> >> > >> >> > >> >> > >> >> - Do you have Forwarding enabled in the Dns server? If no go to the > >> >> Dns > >> >> console -> right click Dns server choose properties -> select > >> >> forwarders > >> >> tab -> Select All other Domains -> got to the Selected domain's > >> >> forwarder > >> >> Ipaddress list and place the ISP Dns server address -> click add -> > >> >> restart > >> >> Dns service. > >> >> > >> >> > >> >> > >> >> Test the resolution on the DC - Go to command prompt and type ping > >> >> www.microsoft.com - check if returns the Ipaddress of the site, then > >> >> go > >> >> to > >> >> the clients and check if the ping command returns the Ipaddress of the > >> >> site. > >> >> > >> >> > >> >> > >> >> > Are you saying I shouldn't have WINS and DNS on the same computer? > >> >> > >> >> > >> >> > >> >> No. What I said was in a Multihomed DC you could have problems with > >> >> Wins > >> >> and > >> >> Dns. > >> >> > >> >> > >> >> > FYI I uninstalled WINS and see the same problem, do I need to > >> >> > remove > >> >> > some > >> >> > records somewhere? > >> >> > >> >> > >> >> > >> >> You'll only need WINS if you're using any APP in your network that > >> >> needs > >> >> NetBIOS resolution or if you have the need to browse over different > >> >> subnets > >> >> using for example Network Places. > >> >> > >> >> > >> >> > >> >> > As for configuring the DNS as you said I already had the interfaces > >> >> > set > >> >> > to > >> >> > only use the local Nic. > >> >> > >> >> > >> >> > >> >> - Great > >> >> > >> >> > >> >> > As for setting the binding order the internal Nic was at the top of > >> >> > the > >> >> > list. How do I check to see if file sharing is only on that NIC? > >> >> > >> >> > >> >> > >> >> - Right click on it and choose properties then you should have the > >> >> "File > >> >> and > >> >> Print Sharing for Microsoft Networks Selected"; however you should > >> >> disable/deselect this on the Public Interface (Security purposes). > >> >> > >> >> > >> >> > I had lowered the windows firewall but there was a Norton Firewall > >> >> > that > >> >> > was > >> >> > preventing Laptop 2 from Filesharing. That now works. So both the > >> >> > desktop > >> >> > and Laptop 2 have the same issues. They get an IP, can perform > >> >> > Fielsharing > >> >> > but can't connect to the internet. > >> >> > >> >> > >> >> > >> >> Check also if is preventing Internet access or any other access to > >> >> server > >> >> or > >> >> Dns, etc. Best practices here are for test DISABLE the Norton Firewall > >> >> and > >> >> test, in this way you can immediately check if this as relation with > >> >> your > >> >> current problems. > >> >> > >> >> > >> >> > >> >> -- > >> >> I hope that the information above helps you > >> >> > >> >> Good Luck > >> >> Jorge Silva > >> >> MCSA > >> >> Systems Administrator > >> >> > >> >> "Greg P" <gsp@newsgroups.nospam> wrote in message > >> >> news:25530004-70F9-484D-A87A-26A6B823685F@microsoft.com... > >> >> > Jorge, > >> >> > > >> >> > What is a multihomed DC? What do I need to change on my server to > >> >> > mave > >> >> > this > >> >> > work? Are you saying I shouldn't have WINS and DNS on the same > >> >> > computer? > >> >> > FYI I uninstalled WINS and see the same problem, do I need to > >> >> > remove > >> >> > some > >> >> > records somewhere? > >> >> > > >> >> > As for configuring the DNS as you said I already had the interfaces > >> >> > set > >> >> > to > >> >> > only use the local nic. > >> >> > > >> >> > As for setting the binding order the internal nic was at the top of > >> >> > the > >> >> > list. How do I check to see if file sharing is only on that NIC? > >> >> > > >> >> > I had lowered the windows firewall but there was a Norton Firewall > >> >> > that > >> >> > was > >> >> > preventing Laptop 2 from Filesharing. That now works. So both the > >> >> > desktop > >> >> > and Laptop 2 have the same issues. They get an IP, can perform > >> >> > Fielsharing FYI I did ping my Gateway (the external nic on my server) and was sucessful.
I realized you might need to know that. Show quoteHide quote "Greg P" wrote: > Yes I am using Remote Access to access the internet. All of your suggustions > worked (got a responce) and my trace gets out to MSN, but internet still > doesn't work. 192..168.10.1 is my server 192.168.10.3 is my desktop (the one > I ran the trace on, but can't use the internet on) below are my pings and > trace. > > Microsoft Windows XP [Version 5.1.2600] > (C) Copyright 1985-2001 Microsoft Corp. > > C:\Documents and Settings\gperrego>ping 127.0.0.1 > > Pinging 127.0.0.1 with 32 bytes of data: > > Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > > Ping statistics for 127.0.0.1: > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > Approximate round trip times in milli-seconds: > Minimum = 0ms, Maximum = 0ms, Average = 0ms > > C:\Documents and Settings\gperrego>ping 192.168.10.1 > > Pinging 192.168.10.1 with 32 bytes of data: > > Reply from 192.168.10.1: bytes=32 time=101ms TTL=128 > Reply from 192.168.10.1: bytes=32 time=174ms TTL=128 > Reply from 192.168.10.1: bytes=32 time=1ms TTL=128 > Reply from 192.168.10.1: bytes=32 time=1ms TTL=128 > > Ping statistics for 192.168.10.1: > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > Approximate round trip times in milli-seconds: > Minimum = 1ms, Maximum = 174ms, Average = 69ms > > C:\Documents and Settings\gperrego>ping 192.168.10.3 > > Pinging 192.168.10.3 with 32 bytes of data: > > Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 > Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 > Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 > Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 > > Ping statistics for 192.168.10.3: > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > Approximate round trip times in milli-seconds: > Minimum = 0ms, Maximum = 0ms, Average = 0ms > > C:\Documents and Settings\gperrego>ping 192.168.10.2 > > Pinging 192.168.10.2 with 32 bytes of data: > > Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 > Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 > Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 > Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 > > Ping statistics for 192.168.10.2: > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > Approximate round trip times in milli-seconds: > Minimum = 0ms, Maximum = 0ms, Average = 0ms > > C:\Documents and Settings\gperrego>tracert www.microsoft.com > > Tracing route to lb1.www.ms.akadns.net [207.46.199.30] > over a maximum of 30 hops: > > 1 1 ms 1 ms 1 ms nugget.sbs.net [192.168.10.1] > 2 7 ms 8 ms 8 ms 10.37.160.1 > 3 8 ms 8 ms 8 ms gig0-2.austtxa-ubr7.austin.rr.com > [24.27.12.81] > > 4 9 ms 9 ms 7 ms gig2-3.austtxa-rtr1.austin.rr.com > [24.27.12.85] > > 5 18 ms 10 ms 9 ms srp0-0.austtxrdc-rtr2.austin.rr.com > [24.27.12.34 > ] > 6 9 ms 8 ms 9 ms pos1-0.austtxrdc-rtr4.texas.rr.com > [66.68.1.110] > > 7 17 ms 18 ms 16 ms son0-0-0.hstqtxl3-rtr1.texas.rr.com > [24.93.33.15 > 3] > 8 18 ms 17 ms 16 ms 4.79.88.21 > 9 16 ms 16 ms 18 ms ge-2-0-0.mp1.Houston1.Level3.net [4.68.97.241] > 10 172 ms 110 ms 60 ms as-1-0.mp2.Seattle1.Level3.net > [209.247.10.133] > > 11 61 ms 61 ms 59 ms ge-2-0-0-52.gar1.Seattle1.Level3.net > [4.68.105.4 > 1] > 12 60 ms 61 ms 62 ms 65.59.235.6 > 13 94 ms 62 ms 62 ms 207.46.37.225 > 14 62 ms 61 ms 63 ms pos1-0.tuk-12ix-1b.ntwk.msn.net > [207.46.36.146] > > 15 60 ms 62 ms 62 ms pos1-0.tke-12ix-1b.ntwk.msn.net [207.46.155.5] > 16 60 ms 60 ms 60 ms po10.tuk-65ns-mcs-1a.ntwk.msn.net > [207.46.224.15 > 1] > 17 * ^C > C:\Documents and Settings\gperrego> > > "Jorge Silva" wrote: > > > The request TimesOut -> normal, the servers in the internet won't reply to > > ping requets because they are protected by firewalls. > > > > Basic Steps to troubleshoot are: > > > > 1. Ping the loopback address to verify that TCP/IP is installed and > > configured correctly on the local computer. To perform this step, enter ping > > 127.0.0.1 at a command prompt. > > > > If the loopback step fails, the IP stack is not responding. This problem > > might be occurring because the TCP drivers are corrupted, the network > > adapter might not be working, or another service might be interfering with > > IP. > > > > > > > > 2. Ping the IP address of the local computer to verify that an address has > > been added correctly. To perform this step, enter ping <IP address of local > > host> at a command prompt. > > > > > > > > 3. Ping the IP address of the default gateway. This step verifies that the > > default gateway is reachable and that the local host can communicate with > > another host on the network. To perform this step, enter ping <IP address of > > default gateway> at a command prompt. > > > > > > > > Then you can use Tracert which is a route-tracing utility that allows you to > > track the path of a forwarded packet from router to router for up to 30 > > hops. Tracert works by sending ICMP echo requests to an IP address, while > > incrementing the Time to Live (TTL) field in the IP header, starting at 1, > > and analyzing the ICMP errors that are returned. Tracert prints out an > > ordered list of the routers in the path that returned these error messages. > > > > > > Type on command prompt: > > <tracert www.microsoft.com> press enter > > > > > > -- > > I hope that the information above helps you > > > > Good Luck > > Jorge Silva > > MCSA > > Systems Administrator > > > > "Greg P" <gsp@newsgroups.nospam> wrote in message > > news:01B390CF-90D6-4305-9008-8E34BE2E69E6@microsoft.com... > > > Jorge, > > > > > > I reset internet options to no avail. One thing i'm not sure about is > > > when > > > I ping the internet from any computer on the network the request times > > > out. > > > Even the server and the laptop that the internet works on. Otherwise I'm > > > totally stumped. > > > > > > Thanks, > > > Greg > > > > > > "Jorge Silva" wrote: > > > > > >> > I uninstalled Norton totally from the desktop. If it can't connect to > > >> > the > > >> > internet I can't get a virus :) > > >> > > >> It looks that your Dns resolution is working well. So the only > > >> explanation > > >> that I can remember at this moment is that there is something or some > > >> filter > > >> that prevents you from going to the internet. Check Internet options or > > >> any > > >> type of configuration internet related that you migh have in your pc. > > >> -- > > >> I hope that the information above helps you > > >> > > >> Good Luck > > >> Jorge Silva > > >> MCSA > > >> Systems Administrator > > >> > > >> "Greg P" <gsp@newsgroups.nospam> wrote in message > > >> news:3BDBCBA0-CDBF-4A47-8B91-B77978A81F49@microsoft.com... > > >> > Jorge, > > >> > > > >> > Unfortunately I'm in the same spot that I started in, except we solved > > >> > the > > >> > file sharing issue on Laptop 2 by lowering the Norton firewall. I > > >> > still > > >> > can't access the internet on the desktop or laptop 2, even though they > > >> > are > > >> > on > > >> > the dame domain as Laptop 1 which can access the internet. With that > > >> > being > > >> > said I'm not sure if you still think this is a DNS problem? > > >> > > > >> >>Well you said that now you have everything working except Internet, and > > >> >>you also said that you don't have Proxy or any other thing that > > >> > prevents/restricts users to access to the internet, so you must have a > > >> > DNS > > >> > resolution problem. > > >> > > > >> >>Do you have Forwarding enabled in the Dns server? > > >> > > > >> > Yes, this is set up with the correct ip addresses. > > >> > > > >> >>Test the resolution on the DC - Go to command prompt and type ping > > >> >>www.microsoft.com - check if returns the Ipaddress of the site > > >> > then go to the clients and check if the ping command returns the > > >> > Ipaddress > > >> > of the site. > > >> > > > >> > All resolve the IP address, all requests time out. > > >> > > > >> >>Right click on it and choose properties then you should have the "File > > >> >>and > > >> >>Print Sharing for Microsoft Networks Selected"; however you should > > >> >>disable/deselect this on the Public Interface (Security purposes). > > >> > > > >> > The File and Print Sharing was selected previously. (there wasn't a > > >> > Public > > >> > Interface option for this nic, there are only 4 options in the > > >> > properties > > >> > page, Client for MS Networks, Network Lad Balancing, File and Printer > > >> > Sharing, and TCP/IP) > > >> > > > >> >>Check also if is preventing Internet access or any other access to > > >> >>server > > >> >>or Dns, etc. Best practices here are for test DISABLE the Norton > > >> >>Firewall > > >> >>and test, in this way you can immediately check if this as relation > > >> >>with > > >> >>your current problems. > > >> > > > >> > I uninstalled Norton totally from the desktop. If it can't connect to > > >> > the > > >> > internet I can't get a virus :) > > >> > > > >> > > > >> > "Jorge Silva" wrote: > > >> > > > >> >> In line > > >> >> > > >> >> > > >> >> > > >> >> > What is a multihomed DC? > > >> >> > > >> >> > > >> >> > > >> >> Is a Domain controller with more than one Nic (Network Interface Card) > > >> >> card > > >> >> > > >> >> > > >> >> > > >> >> > What do I need to change on my server to mave this work? > > >> >> > > >> >> > > >> >> > > >> >> Well you said that now you have everything working except Internet, > > >> >> and > > >> >> you > > >> >> also said that you don't have Proxy or any other thing that > > >> >> prevents/restricts users to access to the internet, so you must have a > > >> >> DNS > > >> >> resolution problem. > > >> >> > > >> >> > > >> >> > > >> >> - Do you have Forwarding enabled in the Dns server? If no go to the > > >> >> Dns > > >> >> console -> right click Dns server choose properties -> select > > >> >> forwarders > > >> >> tab -> Select All other Domains -> got to the Selected domain's > > >> >> forwarder > > >> >> Ipaddress list and place the ISP Dns server address -> click add -> > > >> >> restart > > >> >> Dns service. > > >> >> > > >> >> > > >> >> > > >> >> Test the resolution on the DC - Go to command prompt and type ping > > >> >> www.microsoft.com - check if returns the Ipaddress of the site, then > > >> >> go > > >> >> to > > >> >> the clients and check if the ping command returns the Ipaddress of the > > >> >> site. > > >> >> > > >> >> Check if you have nay filters enabled on the RRAS server.
-- Show quoteHide quoteI hope that the information above helps you Good Luck Jorge Silva MCSA Systems Administrator "Greg P" <gsp@newsgroups.nospam> wrote in message news:11E781ED-0DBA-41F7-86C7-63DDD5A9CB17@microsoft.com... > FYI I did ping my Gateway (the external nic on my server) and was > sucessful. > I realized you might need to know that. > > "Greg P" wrote: > >> Yes I am using Remote Access to access the internet. All of your >> suggustions >> worked (got a responce) and my trace gets out to MSN, but internet still >> doesn't work. 192..168.10.1 is my server 192.168.10.3 is my desktop (the >> one >> I ran the trace on, but can't use the internet on) below are my pings and >> trace. >> >> Microsoft Windows XP [Version 5.1.2600] >> (C) Copyright 1985-2001 Microsoft Corp. >> >> C:\Documents and Settings\gperrego>ping 127.0.0.1 >> >> Pinging 127.0.0.1 with 32 bytes of data: >> >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 >> >> Ping statistics for 127.0.0.1: >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), >> Approximate round trip times in milli-seconds: >> Minimum = 0ms, Maximum = 0ms, Average = 0ms >> >> C:\Documents and Settings\gperrego>ping 192.168.10.1 >> >> Pinging 192.168.10.1 with 32 bytes of data: >> >> Reply from 192.168.10.1: bytes=32 time=101ms TTL=128 >> Reply from 192.168.10.1: bytes=32 time=174ms TTL=128 >> Reply from 192.168.10.1: bytes=32 time=1ms TTL=128 >> Reply from 192.168.10.1: bytes=32 time=1ms TTL=128 >> >> Ping statistics for 192.168.10.1: >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), >> Approximate round trip times in milli-seconds: >> Minimum = 1ms, Maximum = 174ms, Average = 69ms >> >> C:\Documents and Settings\gperrego>ping 192.168.10.3 >> >> Pinging 192.168.10.3 with 32 bytes of data: >> >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 >> >> Ping statistics for 192.168.10.3: >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), >> Approximate round trip times in milli-seconds: >> Minimum = 0ms, Maximum = 0ms, Average = 0ms >> >> C:\Documents and Settings\gperrego>ping 192.168.10.2 >> >> Pinging 192.168.10.2 with 32 bytes of data: >> >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 >> >> Ping statistics for 192.168.10.2: >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), >> Approximate round trip times in milli-seconds: >> Minimum = 0ms, Maximum = 0ms, Average = 0ms >> >> C:\Documents and Settings\gperrego>tracert www.microsoft.com >> >> Tracing route to lb1.www.ms.akadns.net [207.46.199.30] >> over a maximum of 30 hops: >> >> 1 1 ms 1 ms 1 ms nugget.sbs.net [192.168.10.1] >> 2 7 ms 8 ms 8 ms 10.37.160.1 >> 3 8 ms 8 ms 8 ms gig0-2.austtxa-ubr7.austin.rr.com >> [24.27.12.81] >> >> 4 9 ms 9 ms 7 ms gig2-3.austtxa-rtr1.austin.rr.com >> [24.27.12.85] >> >> 5 18 ms 10 ms 9 ms srp0-0.austtxrdc-rtr2.austin.rr.com >> [24.27.12.34 >> ] >> 6 9 ms 8 ms 9 ms pos1-0.austtxrdc-rtr4.texas.rr.com >> [66.68.1.110] >> >> 7 17 ms 18 ms 16 ms son0-0-0.hstqtxl3-rtr1.texas.rr.com >> [24.93.33.15 >> 3] >> 8 18 ms 17 ms 16 ms 4.79.88.21 >> 9 16 ms 16 ms 18 ms ge-2-0-0.mp1.Houston1.Level3.net >> [4.68.97.241] >> 10 172 ms 110 ms 60 ms as-1-0.mp2.Seattle1.Level3.net >> [209.247.10.133] >> >> 11 61 ms 61 ms 59 ms ge-2-0-0-52.gar1.Seattle1.Level3.net >> [4.68.105.4 >> 1] >> 12 60 ms 61 ms 62 ms 65.59.235.6 >> 13 94 ms 62 ms 62 ms 207.46.37.225 >> 14 62 ms 61 ms 63 ms pos1-0.tuk-12ix-1b.ntwk.msn.net >> [207.46.36.146] >> >> 15 60 ms 62 ms 62 ms pos1-0.tke-12ix-1b.ntwk.msn.net >> [207.46.155.5] >> 16 60 ms 60 ms 60 ms po10.tuk-65ns-mcs-1a.ntwk.msn.net >> [207.46.224.15 >> 1] >> 17 * ^C >> C:\Documents and Settings\gperrego> >> >> "Jorge Silva" wrote: >> >> > The request TimesOut -> normal, the servers in the internet won't reply >> > to >> > ping requets because they are protected by firewalls. >> > >> > Basic Steps to troubleshoot are: >> > >> > 1. Ping the loopback address to verify that TCP/IP is installed and >> > configured correctly on the local computer. To perform this step, enter >> > ping >> > 127.0.0.1 at a command prompt. >> > >> > If the loopback step fails, the IP stack is not responding. This >> > problem >> > might be occurring because the TCP drivers are corrupted, the network >> > adapter might not be working, or another service might be interfering >> > with >> > IP. >> > >> > >> > >> > 2. Ping the IP address of the local computer to verify that an address >> > has >> > been added correctly. To perform this step, enter ping <IP address of >> > local >> > host> at a command prompt. >> > >> > >> > >> > 3. Ping the IP address of the default gateway. This step verifies that >> > the >> > default gateway is reachable and that the local host can communicate >> > with >> > another host on the network. To perform this step, enter ping <IP >> > address of >> > default gateway> at a command prompt. >> > >> > >> > >> > Then you can use Tracert which is a route-tracing utility that allows >> > you to >> > track the path of a forwarded packet from router to router for up to 30 >> > hops. Tracert works by sending ICMP echo requests to an IP address, >> > while >> > incrementing the Time to Live (TTL) field in the IP header, starting at >> > 1, >> > and analyzing the ICMP errors that are returned. Tracert prints out an >> > ordered list of the routers in the path that returned these error >> > messages. >> > >> > >> > Type on command prompt: >> > <tracert www.microsoft.com> press enter >> > >> > >> > -- >> > I hope that the information above helps you >> > >> > Good Luck >> > Jorge Silva >> > MCSA >> > Systems Administrator >> > >> > "Greg P" <gsp@newsgroups.nospam> wrote in message >> > news:01B390CF-90D6-4305-9008-8E34BE2E69E6@microsoft.com... >> > > Jorge, >> > > >> > > I reset internet options to no avail. One thing i'm not sure about >> > > is >> > > when >> > > I ping the internet from any computer on the network the request >> > > times >> > > out. >> > > Even the server and the laptop that the internet works on. Otherwise >> > > I'm >> > > totally stumped. >> > > >> > > Thanks, >> > > Greg >> > > >> > > "Jorge Silva" wrote: >> > > >> > >> > I uninstalled Norton totally from the desktop. If it can't >> > >> > connect to >> > >> > the >> > >> > internet I can't get a virus :) >> > >> >> > >> It looks that your Dns resolution is working well. So the only >> > >> explanation >> > >> that I can remember at this moment is that there is something or >> > >> some >> > >> filter >> > >> that prevents you from going to the internet. Check Internet options >> > >> or >> > >> any >> > >> type of configuration internet related that you migh have in your >> > >> pc. >> > >> -- >> > >> I hope that the information above helps you >> > >> >> > >> Good Luck >> > >> Jorge Silva >> > >> MCSA >> > >> Systems Administrator >> > >> >> > >> "Greg P" <gsp@newsgroups.nospam> wrote in message >> > >> news:3BDBCBA0-CDBF-4A47-8B91-B77978A81F49@microsoft.com... >> > >> > Jorge, >> > >> > >> > >> > Unfortunately I'm in the same spot that I started in, except we >> > >> > solved >> > >> > the >> > >> > file sharing issue on Laptop 2 by lowering the Norton firewall. I >> > >> > still >> > >> > can't access the internet on the desktop or laptop 2, even though >> > >> > they >> > >> > are >> > >> > on >> > >> > the dame domain as Laptop 1 which can access the internet. With >> > >> > that >> > >> > being >> > >> > said I'm not sure if you still think this is a DNS problem? >> > >> > >> > >> >>Well you said that now you have everything working except >> > >> >>Internet, and >> > >> >>you also said that you don't have Proxy or any other thing that >> > >> > prevents/restricts users to access to the internet, so you must >> > >> > have a >> > >> > DNS >> > >> > resolution problem. >> > >> > >> > >> >>Do you have Forwarding enabled in the Dns server? >> > >> > >> > >> > Yes, this is set up with the correct ip addresses. >> > >> > >> > >> >>Test the resolution on the DC - Go to command prompt and type ping >> > >> >>www.microsoft.com - check if returns the Ipaddress of the site >> > >> > then go to the clients and check if the ping command returns the >> > >> > Ipaddress >> > >> > of the site. >> > >> > >> > >> > All resolve the IP address, all requests time out. >> > >> > >> > >> >>Right click on it and choose properties then you should have the >> > >> >>"File >> > >> >>and >> > >> >>Print Sharing for Microsoft Networks Selected"; however you should >> > >> >>disable/deselect this on the Public Interface (Security purposes). >> > >> > >> > >> > The File and Print Sharing was selected previously. (there wasn't >> > >> > a >> > >> > Public >> > >> > Interface option for this nic, there are only 4 options in the >> > >> > properties >> > >> > page, Client for MS Networks, Network Lad Balancing, File and >> > >> > Printer >> > >> > Sharing, and TCP/IP) >> > >> > >> > >> >>Check also if is preventing Internet access or any other access to >> > >> >>server >> > >> >>or Dns, etc. Best practices here are for test DISABLE the Norton >> > >> >>Firewall >> > >> >>and test, in this way you can immediately check if this as >> > >> >>relation >> > >> >>with >> > >> >>your current problems. >> > >> > >> > >> > I uninstalled Norton totally from the desktop. If it can't >> > >> > connect to >> > >> > the >> > >> > internet I can't get a virus :) >> > >> > >> > >> > >> > >> > "Jorge Silva" wrote: >> > >> > >> > >> >> In line >> > >> >> >> > >> >> >> > >> >> >> > >> >> > What is a multihomed DC? >> > >> >> >> > >> >> >> > >> >> >> > >> >> Is a Domain controller with more than one Nic (Network Interface >> > >> >> Card) >> > >> >> card >> > >> >> >> > >> >> >> > >> >> >> > >> >> > What do I need to change on my server to mave this work? >> > >> >> >> > >> >> >> > >> >> >> > >> >> Well you said that now you have everything working except >> > >> >> Internet, >> > >> >> and >> > >> >> you >> > >> >> also said that you don't have Proxy or any other thing that >> > >> >> prevents/restricts users to access to the internet, so you must >> > >> >> have a >> > >> >> DNS >> > >> >> resolution problem. >> > >> >> >> > >> >> >> > >> >> >> > >> >> - Do you have Forwarding enabled in the Dns server? If no go to >> > >> >> the >> > >> >> Dns >> > >> >> console -> right click Dns server choose properties -> select >> > >> >> forwarders >> > >> >> tab -> Select All other Domains -> got to the Selected domain's >> > >> >> forwarder >> > >> >> Ipaddress list and place the ISP Dns server address -> click >> > >> >> add -> >> > >> >> restart >> > >> >> Dns service. >> > >> >> >> > >> >> >> > >> >> >> > >> >> Test the resolution on the DC - Go to command prompt and type >> > >> >> ping >> > >> >> www.microsoft.com - check if returns the Ipaddress of the site, >> > >> >> then >> > >> >> go >> > >> >> to >> > >> >> the clients and check if the ping command returns the Ipaddress >> > >> >> of the >> > >> >> site. >> > >> >> >> > >> >> No filter, I removed and reconfigured the RRAS many times to no avail.
Show quoteHide quote "Jorge Silva" wrote: > Check if you have nay filters enabled on the RRAS server. > > -- > I hope that the information above helps you > > Good Luck > Jorge Silva > MCSA > Systems Administrator > > "Greg P" <gsp@newsgroups.nospam> wrote in message > news:11E781ED-0DBA-41F7-86C7-63DDD5A9CB17@microsoft.com... > > FYI I did ping my Gateway (the external nic on my server) and was > > sucessful. > > I realized you might need to know that. > > > > "Greg P" wrote: > > > >> Yes I am using Remote Access to access the internet. All of your > >> suggustions > >> worked (got a responce) and my trace gets out to MSN, but internet still > >> doesn't work. 192..168.10.1 is my server 192.168.10.3 is my desktop (the > >> one > >> I ran the trace on, but can't use the internet on) below are my pings and > >> trace. > >> > >> Microsoft Windows XP [Version 5.1.2600] > >> (C) Copyright 1985-2001 Microsoft Corp. > >> > >> C:\Documents and Settings\gperrego>ping 127.0.0.1 > >> > >> Pinging 127.0.0.1 with 32 bytes of data: > >> > >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > >> > >> Ping statistics for 127.0.0.1: > >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > >> Approximate round trip times in milli-seconds: > >> Minimum = 0ms, Maximum = 0ms, Average = 0ms > >> > >> C:\Documents and Settings\gperrego>ping 192.168.10.1 > >> > >> Pinging 192.168.10.1 with 32 bytes of data: > >> > >> Reply from 192.168.10.1: bytes=32 time=101ms TTL=128 > >> Reply from 192.168.10.1: bytes=32 time=174ms TTL=128 > >> Reply from 192.168.10.1: bytes=32 time=1ms TTL=128 > >> Reply from 192.168.10.1: bytes=32 time=1ms TTL=128 > >> > >> Ping statistics for 192.168.10.1: > >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > >> Approximate round trip times in milli-seconds: > >> Minimum = 1ms, Maximum = 174ms, Average = 69ms > >> > >> C:\Documents and Settings\gperrego>ping 192.168.10.3 > >> > >> Pinging 192.168.10.3 with 32 bytes of data: > >> > >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 > >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 > >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 > >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 > >> > >> Ping statistics for 192.168.10.3: > >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > >> Approximate round trip times in milli-seconds: > >> Minimum = 0ms, Maximum = 0ms, Average = 0ms > >> > >> C:\Documents and Settings\gperrego>ping 192.168.10.2 > >> > >> Pinging 192.168.10.2 with 32 bytes of data: > >> > >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 > >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 > >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 > >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 > >> > >> Ping statistics for 192.168.10.2: > >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > >> Approximate round trip times in milli-seconds: > >> Minimum = 0ms, Maximum = 0ms, Average = 0ms > >> > >> C:\Documents and Settings\gperrego>tracert www.microsoft.com > >> > >> Tracing route to lb1.www.ms.akadns.net [207.46.199.30] > >> over a maximum of 30 hops: > >> > >> 1 1 ms 1 ms 1 ms nugget.sbs.net [192.168.10.1] > >> 2 7 ms 8 ms 8 ms 10.37.160.1 > >> 3 8 ms 8 ms 8 ms gig0-2.austtxa-ubr7.austin.rr.com > >> [24.27.12.81] > >> > >> 4 9 ms 9 ms 7 ms gig2-3.austtxa-rtr1.austin.rr.com > >> [24.27.12.85] > >> > >> 5 18 ms 10 ms 9 ms srp0-0.austtxrdc-rtr2.austin.rr.com > >> [24.27.12.34 > >> ] > >> 6 9 ms 8 ms 9 ms pos1-0.austtxrdc-rtr4.texas.rr.com > >> [66.68.1.110] > >> > >> 7 17 ms 18 ms 16 ms son0-0-0.hstqtxl3-rtr1.texas.rr.com > >> [24.93.33.15 > >> 3] > >> 8 18 ms 17 ms 16 ms 4.79.88.21 > >> 9 16 ms 16 ms 18 ms ge-2-0-0.mp1.Houston1.Level3.net > >> [4.68.97.241] > >> 10 172 ms 110 ms 60 ms as-1-0.mp2.Seattle1.Level3.net > >> [209.247.10.133] > >> > >> 11 61 ms 61 ms 59 ms ge-2-0-0-52.gar1.Seattle1.Level3.net > >> [4.68.105.4 > >> 1] > >> 12 60 ms 61 ms 62 ms 65.59.235.6 > >> 13 94 ms 62 ms 62 ms 207.46.37.225 > >> 14 62 ms 61 ms 63 ms pos1-0.tuk-12ix-1b.ntwk.msn.net > >> [207.46.36.146] > >> > >> 15 60 ms 62 ms 62 ms pos1-0.tke-12ix-1b.ntwk.msn.net > >> [207.46.155.5] > >> 16 60 ms 60 ms 60 ms po10.tuk-65ns-mcs-1a.ntwk.msn.net > >> [207.46.224.15 > >> 1] > >> 17 * ^C > >> C:\Documents and Settings\gperrego> > >> > >> "Jorge Silva" wrote: > >> > >> > The request TimesOut -> normal, the servers in the internet won't reply > >> > to > >> > ping requets because they are protected by firewalls. > >> > > >> > Basic Steps to troubleshoot are: > >> > > >> > 1. Ping the loopback address to verify that TCP/IP is installed and > >> > configured correctly on the local computer. To perform this step, enter > >> > ping > >> > 127.0.0.1 at a command prompt. > >> > > >> > If the loopback step fails, the IP stack is not responding. This > >> > problem > >> > might be occurring because the TCP drivers are corrupted, the network > >> > adapter might not be working, or another service might be interfering > >> > with > >> > IP. > >> > > >> > > >> > > >> > 2. Ping the IP address of the local computer to verify that an address > >> > has > >> > been added correctly. To perform this step, enter ping <IP address of > >> > local > >> > host> at a command prompt. > >> > > >> > > >> > > >> > 3. Ping the IP address of the default gateway. This step verifies that > >> > the > >> > default gateway is reachable and that the local host can communicate > >> > with > >> > another host on the network. To perform this step, enter ping <IP > >> > address of > >> > default gateway> at a command prompt. > >> > > >> > > >> > > >> > Then you can use Tracert which is a route-tracing utility that allows > >> > you to > >> > track the path of a forwarded packet from router to router for up to 30 > >> > hops. Tracert works by sending ICMP echo requests to an IP address, > >> > while > >> > incrementing the Time to Live (TTL) field in the IP header, starting at > >> > 1, > >> > and analyzing the ICMP errors that are returned. Tracert prints out an > >> > ordered list of the routers in the path that returned these error > >> > messages. > >> > > >> > > >> > Type on command prompt: > >> > <tracert www.microsoft.com> press enter > >> > > >> > > >> > -- > >> > I hope that the information above helps you > >> > > >> > Good Luck > >> > Jorge Silva > >> > MCSA > >> > Systems Administrator > >> > > >> > "Greg P" <gsp@newsgroups.nospam> wrote in message > >> > news:01B390CF-90D6-4305-9008-8E34BE2E69E6@microsoft.com... > >> > > Jorge, > >> > > > >> > > I reset internet options to no avail. One thing i'm not sure about > >> > > is > >> > > when > >> > > I ping the internet from any computer on the network the request > >> > > times > >> > > out. > >> > > Even the server and the laptop that the internet works on. Otherwise > >> > > I'm > >> > > totally stumped. > >> > > > >> > > Thanks, > >> > > Greg > >> > > > >> > > "Jorge Silva" wrote: > >> > > > >> > >> > I uninstalled Norton totally from the desktop. If it can't > >> > >> > connect to > >> > >> > the > >> > >> > internet I can't get a virus :) > >> > >> > >> > >> It looks that your Dns resolution is working well. So the only > >> > >> explanation > >> > >> that I can remember at this moment is that there is something or > >> > >> some > >> > >> filter > >> > >> that prevents you from going to the internet. Check Internet options > >> > >> or > >> > >> any > >> > >> type of configuration internet related that you migh have in your > >> > >> pc. > >> > >> -- > >> > >> I hope that the information above helps you > >> > >> > >> > >> Good Luck > >> > >> Jorge Silva > >> > >> MCSA > >> > >> Systems Administrator > >> > >> > >> > >> "Greg P" <gsp@newsgroups.nospam> wrote in message > >> > >> news:3BDBCBA0-CDBF-4A47-8B91-B77978A81F49@microsoft.com... > >> > >> > Jorge, > >> > >> > > >> > >> > Unfortunately I'm in the same spot that I started in, except we > >> > >> > solved > >> > >> > the > >> > >> > file sharing issue on Laptop 2 by lowering the Norton firewall. I > >> > >> > still > >> > >> > can't access the internet on the desktop or laptop 2, even though > >> > >> > they > >> > >> > are > >> > >> > on > >> > >> > the dame domain as Laptop 1 which can access the internet. With > >> > >> > that > >> > >> > being > >> > >> > said I'm not sure if you still think this is a DNS problem? > >> > >> > > >> > >> >>Well you said that now you have everything working except > >> > >> >>Internet, and > >> > >> >>you also said that you don't have Proxy or any other thing that > >> > >> > prevents/restricts users to access to the internet, so you must > >> > >> > have a > >> > >> > DNS > >> > >> > resolution problem. > >> > >> > > >> > >> >>Do you have Forwarding enabled in the Dns server? > >> > >> > > >> > >> > Yes, this is set up with the correct ip addresses. > >> > >> > > >> > >> >>Test the resolution on the DC - Go to command prompt and type ping > >> > >> >>www.microsoft.com - check if returns the Ipaddress of the site > >> > >> > then go to the clients and check if the ping command returns the > >> > >> > Ipaddress > >> > >> > of the site. > >> > >> > > >> > >> > All resolve the IP address, all requests time out. > >> > >> > > >> > >> >>Right click on it and choose properties then you should have the > >> > >> >>"File > >> > >> >>and > >> > >> >>Print Sharing for Microsoft Networks Selected"; however you should > >> > >> >>disable/deselect this on the Public Interface (Security purposes). > >> > >> > > >> > >> > The File and Print Sharing was selected previously. (there wasn't > >> > >> > a > >> > >> > Public > >> > >> > Interface option for this nic, there are only 4 options in the > >> > >> > properties > >> > >> > page, Client for MS Networks, Network Lad Balancing, File and > >> > >> > Printer > >> > >> > Sharing, and TCP/IP) > >> > >> > > >> > >> >>Check also if is preventing Internet access or any other access to > >> > >> >>server > >> > >> >>or Dns, etc. Best practices here are for test DISABLE the Norton > >> > >> >>Firewall > >> > >> >>and test, in this way you can immediately check if this as > >> > >> >>relation > >> > >> >>with > >> > >> >>your current problems. > >> > >> > > >> > >> > I uninstalled Norton totally from the desktop. If it can't > >> > >> > connect to > >> > >> > the Jorge,
It works!! and this has to be a bug!!! When configuring RRAS if I have the RRAS firewall enabled I have the problem, If i remove the basic firewall when configuring RRAS it doesn't work. Why this only effect the two other computers and not my laptop makes no sense to me, although there has to be a reason. But this has to be a bug, if the firewall doesn't allow certain clients to receive the reply from the web site, dont' you think? Thanks, Show quoteHide quote "Jorge Silva" wrote: > Check if you have nay filters enabled on the RRAS server. > > -- > I hope that the information above helps you > > Good Luck > Jorge Silva > MCSA > Systems Administrator > > "Greg P" <gsp@newsgroups.nospam> wrote in message > news:11E781ED-0DBA-41F7-86C7-63DDD5A9CB17@microsoft.com... > > FYI I did ping my Gateway (the external nic on my server) and was > > sucessful. > > I realized you might need to know that. > > > > "Greg P" wrote: > > > >> Yes I am using Remote Access to access the internet. All of your > >> suggustions > >> worked (got a responce) and my trace gets out to MSN, but internet still > >> doesn't work. 192..168.10.1 is my server 192.168.10.3 is my desktop (the > >> one > >> I ran the trace on, but can't use the internet on) below are my pings and > >> trace. > >> > >> Microsoft Windows XP [Version 5.1.2600] > >> (C) Copyright 1985-2001 Microsoft Corp. > >> > >> C:\Documents and Settings\gperrego>ping 127.0.0.1 > >> > >> Pinging 127.0.0.1 with 32 bytes of data: > >> > >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > >> > >> Ping statistics for 127.0.0.1: > >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > >> Approximate round trip times in milli-seconds: > >> Minimum = 0ms, Maximum = 0ms, Average = 0ms > >> > >> C:\Documents and Settings\gperrego>ping 192.168.10.1 > >> > >> Pinging 192.168.10.1 with 32 bytes of data: > >> > >> Reply from 192.168.10.1: bytes=32 time=101ms TTL=128 > >> Reply from 192.168.10.1: bytes=32 time=174ms TTL=128 > >> Reply from 192.168.10.1: bytes=32 time=1ms TTL=128 > >> Reply from 192.168.10.1: bytes=32 time=1ms TTL=128 > >> > >> Ping statistics for 192.168.10.1: > >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > >> Approximate round trip times in milli-seconds: > >> Minimum = 1ms, Maximum = 174ms, Average = 69ms > >> > >> C:\Documents and Settings\gperrego>ping 192.168.10.3 > >> > >> Pinging 192.168.10.3 with 32 bytes of data: > >> > >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 > >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 > >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 > >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 > >> > >> Ping statistics for 192.168.10.3: > >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > >> Approximate round trip times in milli-seconds: > >> Minimum = 0ms, Maximum = 0ms, Average = 0ms > >> > >> C:\Documents and Settings\gperrego>ping 192.168.10.2 > >> > >> Pinging 192.168.10.2 with 32 bytes of data: > >> > >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 > >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 > >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 > >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 > >> > >> Ping statistics for 192.168.10.2: > >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > >> Approximate round trip times in milli-seconds: > >> Minimum = 0ms, Maximum = 0ms, Average = 0ms > >> > >> C:\Documents and Settings\gperrego>tracert www.microsoft.com > >> > >> Tracing route to lb1.www.ms.akadns.net [207.46.199.30] > >> over a maximum of 30 hops: > >> > >> 1 1 ms 1 ms 1 ms nugget.sbs.net [192.168.10.1] > >> 2 7 ms 8 ms 8 ms 10.37.160.1 > >> 3 8 ms 8 ms 8 ms gig0-2.austtxa-ubr7.austin.rr.com > >> [24.27.12.81] > >> > >> 4 9 ms 9 ms 7 ms gig2-3.austtxa-rtr1.austin.rr.com > >> [24.27.12.85] > >> > >> 5 18 ms 10 ms 9 ms srp0-0.austtxrdc-rtr2.austin.rr.com > >> [24.27.12.34 > >> ] > >> 6 9 ms 8 ms 9 ms pos1-0.austtxrdc-rtr4.texas.rr.com > >> [66.68.1.110] > >> > >> 7 17 ms 18 ms 16 ms son0-0-0.hstqtxl3-rtr1.texas.rr.com > >> [24.93.33.15 > >> 3] > >> 8 18 ms 17 ms 16 ms 4.79.88.21 > >> 9 16 ms 16 ms 18 ms ge-2-0-0.mp1.Houston1.Level3.net > >> [4.68.97.241] > >> 10 172 ms 110 ms 60 ms as-1-0.mp2.Seattle1.Level3.net > >> [209.247.10.133] > >> > >> 11 61 ms 61 ms 59 ms ge-2-0-0-52.gar1.Seattle1.Level3.net > >> [4.68.105.4 > >> 1] > >> 12 60 ms 61 ms 62 ms 65.59.235.6 > >> 13 94 ms 62 ms 62 ms 207.46.37.225 > >> 14 62 ms 61 ms 63 ms pos1-0.tuk-12ix-1b.ntwk.msn.net > >> [207.46.36.146] > >> > >> 15 60 ms 62 ms 62 ms pos1-0.tke-12ix-1b.ntwk.msn.net > >> [207.46.155.5] > >> 16 60 ms 60 ms 60 ms po10.tuk-65ns-mcs-1a.ntwk.msn.net > >> [207.46.224.15 > >> 1] > >> 17 * ^C > >> C:\Documents and Settings\gperrego> > >> > >> "Jorge Silva" wrote: > >> > >> > The request TimesOut -> normal, the servers in the internet won't reply > >> > to > >> > ping requets because they are protected by firewalls. > >> > > >> > Basic Steps to troubleshoot are: > >> > > >> > 1. Ping the loopback address to verify that TCP/IP is installed and > >> > configured correctly on the local computer. To perform this step, enter > >> > ping > >> > 127.0.0.1 at a command prompt. > >> > > >> > If the loopback step fails, the IP stack is not responding. This > >> > problem > >> > might be occurring because the TCP drivers are corrupted, the network > >> > adapter might not be working, or another service might be interfering > >> > with > >> > IP. > >> > > >> > > >> > > >> > 2. Ping the IP address of the local computer to verify that an address > >> > has > >> > been added correctly. To perform this step, enter ping <IP address of > >> > local > >> > host> at a command prompt. > >> > > >> > > >> > > >> > 3. Ping the IP address of the default gateway. This step verifies that > >> > the > >> > default gateway is reachable and that the local host can communicate > >> > with > >> > another host on the network. To perform this step, enter ping <IP > >> > address of > >> > default gateway> at a command prompt. > >> > > >> > > >> > > >> > Then you can use Tracert which is a route-tracing utility that allows > >> > you to > >> > track the path of a forwarded packet from router to router for up to 30 > >> > hops. Tracert works by sending ICMP echo requests to an IP address, > >> > while > >> > incrementing the Time to Live (TTL) field in the IP header, starting at > >> > 1, > >> > and analyzing the ICMP errors that are returned. Tracert prints out an > >> > ordered list of the routers in the path that returned these error > >> > messages. > >> > > >> > > >> > Type on command prompt: > >> > <tracert www.microsoft.com> press enter > >> > > >> > > >> > -- > >> > I hope that the information above helps you > >> > > >> > Good Luck > >> > Jorge Silva > >> > MCSA > >> > Systems Administrator > >> > > >> > "Greg P" <gsp@newsgroups.nospam> wrote in message > >> > news:01B390CF-90D6-4305-9008-8E34BE2E69E6@microsoft.com... > >> > > Jorge, > >> > > > >> > > I reset internet options to no avail. One thing i'm not sure about > >> > > is > >> > > when > >> > > I ping the internet from any computer on the network the request > >> > > times > >> > > out. > >> > > Even the server and the laptop that the internet works on. Otherwise > >> > > I'm > >> > > totally stumped. > >> > > > >> > > Thanks, > >> > > Greg > >> > > > >> > > "Jorge Silva" wrote: > >> > > > >> > >> > I uninstalled Norton totally from the desktop. If it can't > >> > >> > connect to > >> > >> > the > >> > >> > internet I can't get a virus :) > >> > >> > >> > >> It looks that your Dns resolution is working well. So the only > >> > >> explanation > >> > >> that I can remember at this moment is that there is something or > >> > >> some > >> > >> filter > >> > >> that prevents you from going to the internet. Check Internet options > >> > >> or > >> > >> any > >> > >> type of configuration internet related that you migh have in your > >> > >> pc. > >> > >> -- > >> > >> I hope that the information above helps you > >> > >> > >> > >> Good Luck > >> > >> Jorge Silva > >> > >> MCSA > >> > >> Systems Administrator > >> > >> > >> > >> "Greg P" <gsp@newsgroups.nospam> wrote in message > >> > >> news:3BDBCBA0-CDBF-4A47-8B91-B77978A81F49@microsoft.com... > >> > >> > Jorge, > >> > >> > > >> > >> > Unfortunately I'm in the same spot that I started in, except we > >> > >> > solved > >> > >> > the > >> > >> > file sharing issue on Laptop 2 by lowering the Norton firewall. I > >> > >> > still > >> > >> > can't access the internet on the desktop or laptop 2, even though > >> > >> > they > >> > >> > are > >> > >> > on > >> > >> > the dame domain as Laptop 1 which can access the internet. With > >> > >> > that > >> > >> > being > >> > >> > said I'm not sure if you still think this is a DNS problem? > >> > >> > > >> > >> >>Well you said that now you have everything working except > >> > >> >>Internet, and > >> > >> >>you also said that you don't have Proxy or any other thing that > >> > >> > prevents/restricts users to access to the internet, so you must > >> > >> > have a > >> > >> > DNS > >> > >> > resolution problem. > >> > >> > > >> > >> >>Do you have Forwarding enabled in the Dns server? > >> > >> > > >> > >> > Yes, this is set up with the correct ip addresses. > >> > >> > > >> > >> >>Test the resolution on the DC - Go to command prompt and type ping > >> > >> >>www.microsoft.com - check if returns the Ipaddress of the site > >> > >> > then go to the clients and check if the ping command returns the > >> > >> > Ipaddress > >> > >> > of the site. > >> > >> > > >> > >> > All resolve the IP address, all requests time out. > >> > >> > > >> > >> >>Right click on it and choose properties then you should have the > >> > >> >>"File > >> > >> >>and > >> > >> >>Print Sharing for Microsoft Networks Selected"; however you should > >> > >> >>disable/deselect this on the Public Interface (Security purposes). > >> > >> > > >> > >> > The File and Print Sharing was selected previously. (there wasn't > >> > >> > a > >> > >> > Public > >> > >> > Interface option for this nic, there are only 4 options in the > >> > >> > properties > >> > >> > page, Client for MS Networks, Network Lad Balancing, File and > >> > >> > Printer > >> > >> > Sharing, and TCP/IP) > >> > >> > > >> > >> >>Check also if is preventing Internet access or any other access to > >> > >> >>server > >> > >> >>or Dns, etc. Best practices here are for test DISABLE the Norton > >> > >> >>Firewall > >> > >> >>and test, in this way you can immediately check if this as > >> > >> >>relation > >> > >> >>with > >> > >> >>your current problems. > >> > >> > > >> > >> > I uninstalled Norton totally from the desktop. If it can't > >> > >> > connect to > >> > >> > the Very strange....
DON'T REMOVE THE FIREWAL. I already setup several RRAS servers and they work fine, were did you enable the Basic Firewal (In the internal Interface or in the Public Interface)? -- Show quoteHide quoteI hope that the information above helps you Good Luck Jorge Silva MCSA Systems Administrator "Greg P" <gsp@newsgroups.nospam> wrote in message news:6E45E005-53B4-4674-9196-0198A6449A17@microsoft.com... > Jorge, > > It works!! and this has to be a bug!!! When configuring RRAS if I have > the > RRAS firewall enabled I have the problem, If i remove the basic firewall > when > configuring RRAS it doesn't work. > > Why this only effect the two other computers and not my laptop makes no > sense to me, although there has to be a reason. But this has to be a bug, > if > the firewall doesn't allow certain clients to receive the reply from the > web > site, dont' you think? > > Thanks, > > "Jorge Silva" wrote: > >> Check if you have nay filters enabled on the RRAS server. >> >> -- >> I hope that the information above helps you >> >> Good Luck >> Jorge Silva >> MCSA >> Systems Administrator >> >> "Greg P" <gsp@newsgroups.nospam> wrote in message >> news:11E781ED-0DBA-41F7-86C7-63DDD5A9CB17@microsoft.com... >> > FYI I did ping my Gateway (the external nic on my server) and was >> > sucessful. >> > I realized you might need to know that. >> > >> > "Greg P" wrote: >> > >> >> Yes I am using Remote Access to access the internet. All of your >> >> suggustions >> >> worked (got a responce) and my trace gets out to MSN, but internet >> >> still >> >> doesn't work. 192..168.10.1 is my server 192.168.10.3 is my desktop >> >> (the >> >> one >> >> I ran the trace on, but can't use the internet on) below are my pings >> >> and >> >> trace. >> >> >> >> Microsoft Windows XP [Version 5.1.2600] >> >> (C) Copyright 1985-2001 Microsoft Corp. >> >> >> >> C:\Documents and Settings\gperrego>ping 127.0.0.1 >> >> >> >> Pinging 127.0.0.1 with 32 bytes of data: >> >> >> >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 >> >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 >> >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 >> >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 >> >> >> >> Ping statistics for 127.0.0.1: >> >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), >> >> Approximate round trip times in milli-seconds: >> >> Minimum = 0ms, Maximum = 0ms, Average = 0ms >> >> >> >> C:\Documents and Settings\gperrego>ping 192.168.10.1 >> >> >> >> Pinging 192.168.10.1 with 32 bytes of data: >> >> >> >> Reply from 192.168.10.1: bytes=32 time=101ms TTL=128 >> >> Reply from 192.168.10.1: bytes=32 time=174ms TTL=128 >> >> Reply from 192.168.10.1: bytes=32 time=1ms TTL=128 >> >> Reply from 192.168.10.1: bytes=32 time=1ms TTL=128 >> >> >> >> Ping statistics for 192.168.10.1: >> >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), >> >> Approximate round trip times in milli-seconds: >> >> Minimum = 1ms, Maximum = 174ms, Average = 69ms >> >> >> >> C:\Documents and Settings\gperrego>ping 192.168.10.3 >> >> >> >> Pinging 192.168.10.3 with 32 bytes of data: >> >> >> >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 >> >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 >> >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 >> >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 >> >> >> >> Ping statistics for 192.168.10.3: >> >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), >> >> Approximate round trip times in milli-seconds: >> >> Minimum = 0ms, Maximum = 0ms, Average = 0ms >> >> >> >> C:\Documents and Settings\gperrego>ping 192.168.10.2 >> >> >> >> Pinging 192.168.10.2 with 32 bytes of data: >> >> >> >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 >> >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 >> >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 >> >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 >> >> >> >> Ping statistics for 192.168.10.2: >> >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), >> >> Approximate round trip times in milli-seconds: >> >> Minimum = 0ms, Maximum = 0ms, Average = 0ms >> >> >> >> C:\Documents and Settings\gperrego>tracert www.microsoft.com >> >> >> >> Tracing route to lb1.www.ms.akadns.net [207.46.199.30] >> >> over a maximum of 30 hops: >> >> >> >> 1 1 ms 1 ms 1 ms nugget.sbs.net [192.168.10.1] >> >> 2 7 ms 8 ms 8 ms 10.37.160.1 >> >> 3 8 ms 8 ms 8 ms gig0-2.austtxa-ubr7.austin.rr.com >> >> [24.27.12.81] >> >> >> >> 4 9 ms 9 ms 7 ms gig2-3.austtxa-rtr1.austin.rr.com >> >> [24.27.12.85] >> >> >> >> 5 18 ms 10 ms 9 ms srp0-0.austtxrdc-rtr2.austin.rr.com >> >> [24.27.12.34 >> >> ] >> >> 6 9 ms 8 ms 9 ms pos1-0.austtxrdc-rtr4.texas.rr.com >> >> [66.68.1.110] >> >> >> >> 7 17 ms 18 ms 16 ms son0-0-0.hstqtxl3-rtr1.texas.rr.com >> >> [24.93.33.15 >> >> 3] >> >> 8 18 ms 17 ms 16 ms 4.79.88.21 >> >> 9 16 ms 16 ms 18 ms ge-2-0-0.mp1.Houston1.Level3.net >> >> [4.68.97.241] >> >> 10 172 ms 110 ms 60 ms as-1-0.mp2.Seattle1.Level3.net >> >> [209.247.10.133] >> >> >> >> 11 61 ms 61 ms 59 ms ge-2-0-0-52.gar1.Seattle1.Level3.net >> >> [4.68.105.4 >> >> 1] >> >> 12 60 ms 61 ms 62 ms 65.59.235.6 >> >> 13 94 ms 62 ms 62 ms 207.46.37.225 >> >> 14 62 ms 61 ms 63 ms pos1-0.tuk-12ix-1b.ntwk.msn.net >> >> [207.46.36.146] >> >> >> >> 15 60 ms 62 ms 62 ms pos1-0.tke-12ix-1b.ntwk.msn.net >> >> [207.46.155.5] >> >> 16 60 ms 60 ms 60 ms po10.tuk-65ns-mcs-1a.ntwk.msn.net >> >> [207.46.224.15 >> >> 1] >> >> 17 * ^C >> >> C:\Documents and Settings\gperrego> >> >> >> >> "Jorge Silva" wrote: >> >> >> >> > The request TimesOut -> normal, the servers in the internet won't >> >> > reply >> >> > to >> >> > ping requets because they are protected by firewalls. >> >> > >> >> > Basic Steps to troubleshoot are: >> >> > >> >> > 1. Ping the loopback address to verify that TCP/IP is installed and >> >> > configured correctly on the local computer. To perform this step, >> >> > enter >> >> > ping >> >> > 127.0.0.1 at a command prompt. >> >> > >> >> > If the loopback step fails, the IP stack is not responding. This >> >> > problem >> >> > might be occurring because the TCP drivers are corrupted, the >> >> > network >> >> > adapter might not be working, or another service might be >> >> > interfering >> >> > with >> >> > IP. >> >> > >> >> > >> >> > >> >> > 2. Ping the IP address of the local computer to verify that an >> >> > address >> >> > has >> >> > been added correctly. To perform this step, enter ping <IP address >> >> > of >> >> > local >> >> > host> at a command prompt. >> >> > >> >> > >> >> > >> >> > 3. Ping the IP address of the default gateway. This step verifies >> >> > that >> >> > the >> >> > default gateway is reachable and that the local host can communicate >> >> > with >> >> > another host on the network. To perform this step, enter ping <IP >> >> > address of >> >> > default gateway> at a command prompt. >> >> > >> >> > >> >> > >> >> > Then you can use Tracert which is a route-tracing utility that >> >> > allows >> >> > you to >> >> > track the path of a forwarded packet from router to router for up to >> >> > 30 >> >> > hops. Tracert works by sending ICMP echo requests to an IP address, >> >> > while >> >> > incrementing the Time to Live (TTL) field in the IP header, starting >> >> > at >> >> > 1, >> >> > and analyzing the ICMP errors that are returned. Tracert prints out >> >> > an >> >> > ordered list of the routers in the path that returned these error >> >> > messages. >> >> > >> >> > >> >> > Type on command prompt: >> >> > <tracert www.microsoft.com> press enter >> >> > >> >> > >> >> > -- >> >> > I hope that the information above helps you >> >> > >> >> > Good Luck >> >> > Jorge Silva >> >> > MCSA >> >> > Systems Administrator >> >> > >> >> > "Greg P" <gsp@newsgroups.nospam> wrote in message >> >> > news:01B390CF-90D6-4305-9008-8E34BE2E69E6@microsoft.com... >> >> > > Jorge, >> >> > > >> >> > > I reset internet options to no avail. One thing i'm not sure >> >> > > about >> >> > > is >> >> > > when >> >> > > I ping the internet from any computer on the network the request >> >> > > times >> >> > > out. >> >> > > Even the server and the laptop that the internet works on. >> >> > > Otherwise >> >> > > I'm >> >> > > totally stumped. >> >> > > >> >> > > Thanks, >> >> > > Greg >> >> > > >> >> > > "Jorge Silva" wrote: >> >> > > >> >> > >> > I uninstalled Norton totally from the desktop. If it can't >> >> > >> > connect to >> >> > >> > the >> >> > >> > internet I can't get a virus :) >> >> > >> >> >> > >> It looks that your Dns resolution is working well. So the only >> >> > >> explanation >> >> > >> that I can remember at this moment is that there is something or >> >> > >> some >> >> > >> filter >> >> > >> that prevents you from going to the internet. Check Internet >> >> > >> options >> >> > >> or >> >> > >> any >> >> > >> type of configuration internet related that you migh have in your >> >> > >> pc. >> >> > >> -- >> >> > >> I hope that the information above helps you >> >> > >> >> >> > >> Good Luck >> >> > >> Jorge Silva >> >> > >> MCSA >> >> > >> Systems Administrator >> >> > >> >> >> > >> "Greg P" <gsp@newsgroups.nospam> wrote in message >> >> > >> news:3BDBCBA0-CDBF-4A47-8B91-B77978A81F49@microsoft.com... >> >> > >> > Jorge, >> >> > >> > >> >> > >> > Unfortunately I'm in the same spot that I started in, except we >> >> > >> > solved >> >> > >> > the >> >> > >> > file sharing issue on Laptop 2 by lowering the Norton firewall. >> >> > >> > I >> >> > >> > still >> >> > >> > can't access the internet on the desktop or laptop 2, even >> >> > >> > though >> >> > >> > they >> >> > >> > are >> >> > >> > on >> >> > >> > the dame domain as Laptop 1 which can access the internet. >> >> > >> > With >> >> > >> > that >> >> > >> > being >> >> > >> > said I'm not sure if you still think this is a DNS problem? >> >> > >> > >> >> > >> >>Well you said that now you have everything working except >> >> > >> >>Internet, and >> >> > >> >>you also said that you don't have Proxy or any other thing that >> >> > >> > prevents/restricts users to access to the internet, so you must >> >> > >> > have a >> >> > >> > DNS >> >> > >> > resolution problem. >> >> > >> > >> >> > >> >>Do you have Forwarding enabled in the Dns server? >> >> > >> > >> >> > >> > Yes, this is set up with the correct ip addresses. >> >> > >> > >> >> > >> >>Test the resolution on the DC - Go to command prompt and type >> >> > >> >>ping >> >> > >> >>www.microsoft.com - check if returns the Ipaddress of the site >> >> > >> > then go to the clients and check if the ping command returns >> >> > >> > the >> >> > >> > Ipaddress >> >> > >> > of the site. >> >> > >> > >> >> > >> > All resolve the IP address, all requests time out. >> >> > >> > >> >> > >> >>Right click on it and choose properties then you should have >> >> > >> >>the >> >> > >> >>"File >> >> > >> >>and >> >> > >> >>Print Sharing for Microsoft Networks Selected"; however you >> >> > >> >>should >> >> > >> >>disable/deselect this on the Public Interface (Security >> >> > >> >>purposes). >> >> > >> > >> >> > >> > The File and Print Sharing was selected previously. (there >> >> > >> > wasn't >> >> > >> > a >> >> > >> > Public >> >> > >> > Interface option for this nic, there are only 4 options in the >> >> > >> > properties >> >> > >> > page, Client for MS Networks, Network Lad Balancing, File and >> >> > >> > Printer >> >> > >> > Sharing, and TCP/IP) >> >> > >> > >> >> > >> >>Check also if is preventing Internet access or any other access >> >> > >> >>to >> >> > >> >>server >> >> > >> >>or Dns, etc. Best practices here are for test DISABLE the >> >> > >> >>Norton >> >> > >> >>Firewall >> >> > >> >>and test, in this way you can immediately check if this as >> >> > >> >>relation >> >> > >> >>with >> >> > >> >>your current problems. >> >> > >> > >> >> > >> > I uninstalled Norton totally from the desktop. If it can't >> >> > >> > connect to >> >> > >> > the I'm sorry I mis-typed there, if I use the firewall it doens't work. If I
uncheck the box when configuring my RRAS then it works correctly?!? This option is only available on the public interface. I just tried to report the issue and was told to send a snail mail letter to Redmond. Thats a little discouraging as I'm sure you would know. Sooooo... I guess I'll write a letter to them. I can easily replicate on this system, although I don't know what is causing it. I'm guessing this product has gone through a ton of testing and this issue would have already been resolved? I don't know what to do. Considering I need to lower my firewalls on my clients for file sharing (which seems weird) the only option I can see is to work with ISA server which I've heard is a big headache in 2003 server but left with no other options I don't think I have a choice. I can't leave my network wide open, that is for sure. Show quoteHide quote "Jorge Silva" wrote: > Very strange.... > > DON'T REMOVE THE FIREWAL. > > I already setup several RRAS servers and they work fine, were did you enable > the Basic Firewal (In the internal Interface or in the Public Interface)? > > -- > I hope that the information above helps you > > Good Luck > Jorge Silva > MCSA > Systems Administrator > > "Greg P" <gsp@newsgroups.nospam> wrote in message > news:6E45E005-53B4-4674-9196-0198A6449A17@microsoft.com... > > Jorge, > > > > It works!! and this has to be a bug!!! When configuring RRAS if I have > > the > > RRAS firewall enabled I have the problem, If i remove the basic firewall > > when > > configuring RRAS it doesn't work. > > > > Why this only effect the two other computers and not my laptop makes no > > sense to me, although there has to be a reason. But this has to be a bug, > > if > > the firewall doesn't allow certain clients to receive the reply from the > > web > > site, dont' you think? > > > > Thanks, > > > > "Jorge Silva" wrote: > > > >> Check if you have nay filters enabled on the RRAS server. > >> > >> -- > >> I hope that the information above helps you > >> > >> Good Luck > >> Jorge Silva > >> MCSA > >> Systems Administrator > >> > >> "Greg P" <gsp@newsgroups.nospam> wrote in message > >> news:11E781ED-0DBA-41F7-86C7-63DDD5A9CB17@microsoft.com... > >> > FYI I did ping my Gateway (the external nic on my server) and was > >> > sucessful. > >> > I realized you might need to know that. > >> > > >> > "Greg P" wrote: > >> > > >> >> Yes I am using Remote Access to access the internet. All of your > >> >> suggustions > >> >> worked (got a responce) and my trace gets out to MSN, but internet > >> >> still > >> >> doesn't work. 192..168.10.1 is my server 192.168.10.3 is my desktop > >> >> (the > >> >> one > >> >> I ran the trace on, but can't use the internet on) below are my pings > >> >> and > >> >> trace. > >> >> > >> >> Microsoft Windows XP [Version 5.1.2600] > >> >> (C) Copyright 1985-2001 Microsoft Corp. > >> >> > >> >> C:\Documents and Settings\gperrego>ping 127.0.0.1 > >> >> > >> >> Pinging 127.0.0.1 with 32 bytes of data: > >> >> > >> >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > >> >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > >> >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > >> >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > >> >> > >> >> Ping statistics for 127.0.0.1: > >> >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > >> >> Approximate round trip times in milli-seconds: > >> >> Minimum = 0ms, Maximum = 0ms, Average = 0ms > >> >> > >> >> C:\Documents and Settings\gperrego>ping 192.168.10.1 > >> >> > >> >> Pinging 192.168.10.1 with 32 bytes of data: > >> >> > >> >> Reply from 192.168.10.1: bytes=32 time=101ms TTL=128 > >> >> Reply from 192.168.10.1: bytes=32 time=174ms TTL=128 > >> >> Reply from 192.168.10.1: bytes=32 time=1ms TTL=128 > >> >> Reply from 192.168.10.1: bytes=32 time=1ms TTL=128 > >> >> > >> >> Ping statistics for 192.168.10.1: > >> >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > >> >> Approximate round trip times in milli-seconds: > >> >> Minimum = 1ms, Maximum = 174ms, Average = 69ms > >> >> > >> >> C:\Documents and Settings\gperrego>ping 192.168.10.3 > >> >> > >> >> Pinging 192.168.10.3 with 32 bytes of data: > >> >> > >> >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 > >> >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 > >> >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 > >> >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 > >> >> > >> >> Ping statistics for 192.168.10.3: > >> >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > >> >> Approximate round trip times in milli-seconds: > >> >> Minimum = 0ms, Maximum = 0ms, Average = 0ms > >> >> > >> >> C:\Documents and Settings\gperrego>ping 192.168.10.2 > >> >> > >> >> Pinging 192.168.10.2 with 32 bytes of data: > >> >> > >> >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 > >> >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 > >> >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 > >> >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 > >> >> > >> >> Ping statistics for 192.168.10.2: > >> >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > >> >> Approximate round trip times in milli-seconds: > >> >> Minimum = 0ms, Maximum = 0ms, Average = 0ms > >> >> > >> >> C:\Documents and Settings\gperrego>tracert www.microsoft.com > >> >> > >> >> Tracing route to lb1.www.ms.akadns.net [207.46.199.30] > >> >> over a maximum of 30 hops: > >> >> > >> >> 1 1 ms 1 ms 1 ms nugget.sbs.net [192.168.10.1] > >> >> 2 7 ms 8 ms 8 ms 10.37.160.1 > >> >> 3 8 ms 8 ms 8 ms gig0-2.austtxa-ubr7.austin.rr.com > >> >> [24.27.12.81] > >> >> > >> >> 4 9 ms 9 ms 7 ms gig2-3.austtxa-rtr1.austin.rr.com > >> >> [24.27.12.85] > >> >> > >> >> 5 18 ms 10 ms 9 ms srp0-0.austtxrdc-rtr2.austin.rr.com > >> >> [24.27.12.34 > >> >> ] > >> >> 6 9 ms 8 ms 9 ms pos1-0.austtxrdc-rtr4.texas.rr.com > >> >> [66.68.1.110] > >> >> > >> >> 7 17 ms 18 ms 16 ms son0-0-0.hstqtxl3-rtr1.texas.rr.com > >> >> [24.93.33.15 > >> >> 3] > >> >> 8 18 ms 17 ms 16 ms 4.79.88.21 > >> >> 9 16 ms 16 ms 18 ms ge-2-0-0.mp1.Houston1.Level3.net > >> >> [4.68.97.241] > >> >> 10 172 ms 110 ms 60 ms as-1-0.mp2.Seattle1.Level3.net > >> >> [209.247.10.133] > >> >> > >> >> 11 61 ms 61 ms 59 ms ge-2-0-0-52.gar1.Seattle1.Level3.net > >> >> [4.68.105.4 > >> >> 1] > >> >> 12 60 ms 61 ms 62 ms 65.59.235.6 > >> >> 13 94 ms 62 ms 62 ms 207.46.37.225 > >> >> 14 62 ms 61 ms 63 ms pos1-0.tuk-12ix-1b.ntwk.msn.net > >> >> [207.46.36.146] > >> >> > >> >> 15 60 ms 62 ms 62 ms pos1-0.tke-12ix-1b.ntwk.msn.net > >> >> [207.46.155.5] > >> >> 16 60 ms 60 ms 60 ms po10.tuk-65ns-mcs-1a.ntwk.msn.net > >> >> [207.46.224.15 > >> >> 1] > >> >> 17 * ^C > >> >> C:\Documents and Settings\gperrego> > >> >> > >> >> "Jorge Silva" wrote: > >> >> > >> >> > The request TimesOut -> normal, the servers in the internet won't > >> >> > reply > >> >> > to > >> >> > ping requets because they are protected by firewalls. > >> >> > > >> >> > Basic Steps to troubleshoot are: > >> >> > > >> >> > 1. Ping the loopback address to verify that TCP/IP is installed and > >> >> > configured correctly on the local computer. To perform this step, > >> >> > enter > >> >> > ping > >> >> > 127.0.0.1 at a command prompt. > >> >> > > >> >> > If the loopback step fails, the IP stack is not responding. This > >> >> > problem > >> >> > might be occurring because the TCP drivers are corrupted, the > >> >> > network > >> >> > adapter might not be working, or another service might be > >> >> > interfering > >> >> > with > >> >> > IP. > >> >> > > >> >> > > >> >> > > >> >> > 2. Ping the IP address of the local computer to verify that an > >> >> > address > >> >> > has > >> >> > been added correctly. To perform this step, enter ping <IP address > >> >> > of > >> >> > local > >> >> > host> at a command prompt. > >> >> > > >> >> > > >> >> > > >> >> > 3. Ping the IP address of the default gateway. This step verifies > >> >> > that > >> >> > the > >> >> > default gateway is reachable and that the local host can communicate > >> >> > with > >> >> > another host on the network. To perform this step, enter ping <IP > >> >> > address of > >> >> > default gateway> at a command prompt. > >> >> > > >> >> > > >> >> > > >> >> > Then you can use Tracert which is a route-tracing utility that > >> >> > allows > >> >> > you to > >> >> > track the path of a forwarded packet from router to router for up to > >> >> > 30 > >> >> > hops. Tracert works by sending ICMP echo requests to an IP address, > >> >> > while > >> >> > incrementing the Time to Live (TTL) field in the IP header, starting > >> >> > at > >> >> > 1, > >> >> > and analyzing the ICMP errors that are returned. Tracert prints out > >> >> > an > >> >> > ordered list of the routers in the path that returned these error > >> >> > messages. > >> >> > > >> >> > > >> >> > Type on command prompt: > >> >> > <tracert www.microsoft.com> press enter > >> >> > > >> >> > > >> >> > -- > >> >> > I hope that the information above helps you > >> >> > > >> >> > Good Luck > >> >> > Jorge Silva > >> >> > MCSA > >> >> > Systems Administrator > >> >> > > >> >> > "Greg P" <gsp@newsgroups.nospam> wrote in message > >> >> > news:01B390CF-90D6-4305-9008-8E34BE2E69E6@microsoft.com... > >> >> > > Jorge, > >> >> > > > >> >> > > I reset internet options to no avail. One thing i'm not sure > >> >> > > about > >> >> > > is > >> >> > > when > >> >> > > I ping the internet from any computer on the network the request > >> >> > > times > >> >> > > out. > >> >> > > Even the server and the laptop that the internet works on. > >> >> > > Otherwise > >> >> > > I'm > >> >> > > totally stumped. > >> >> > > > >> >> > > Thanks, > >> >> > > Greg > >> >> > > > >> >> > > "Jorge Silva" wrote: > >> >> > > > >> >> > >> > I uninstalled Norton totally from the desktop. If it can't > >> >> > >> > connect to > >> >> > >> > the > >> >> > >> > internet I can't get a virus :) > >> >> > >> > >> >> > >> It looks that your Dns resolution is working well. So the only > >> >> > >> explanation > >> >> > >> that I can remember at this moment is that there is something or > >> >> > >> some > >> >> > >> filter > >> >> > >> that prevents you from going to the internet. Check Internet > >> >> > >> options > >> >> > >> or > >> >> > >> any > >> >> > >> type of configuration internet related that you migh have in your > >> >> > >> pc. > >> >> > >> -- > >> >> > >> I hope that the information above helps you > >> >> > >> > >> >> > >> Good Luck > >> >> > >> Jorge Silva > >> >> > >> MCSA > >> >> > >> Systems Administrator > >> >> > >> > >> >> > >> "Greg P" <gsp@newsgroups.nospam> wrote in message > >> >> > >> news:3BDBCBA0-CDBF-4A47-8B91-B77978A81F49@microsoft.com... > >> >> > >> > Jorge, > >> >> > >> > > >> >> > >> > Unfortunately I'm in the same spot that I started in, except we > >> >> > >> > solved > >> >> > >> > the > >> >> > >> > file sharing issue on Laptop 2 by lowering the Norton firewall. > >> >> > >> > I > >> >> > >> > still > >> >> > >> > can't access the internet on the desktop or laptop 2, even > >> >> > >> > though In my expirience:
- ISA 2004 works perfectly with Windows 2003 - RRAS also works perfectly. I thing you're missing some config step, I found this Article check if it helps you check it: NAT in Windows 2003: Setup and Configuration http://www.windowsnetworking.com/articles_tutorials/NAT_Windows_2003_Setup_Configuration.html -- Show quoteHide quoteI hope that the information above helps you Good Luck Jorge Silva MCSA Systems Administrator "Greg P" <gsp@newsgroups.nospam> wrote in message news:246DE6D5-6FA3-4646-A587-D232A81BA978@microsoft.com... > I'm sorry I mis-typed there, if I use the firewall it doens't work. If I > uncheck the box when configuring my RRAS then it works correctly?!? This > option is only available on the public interface. > > I just tried to report the issue and was told to send a snail mail letter > to > Redmond. Thats a little discouraging as I'm sure you would know. > Sooooo... > I guess I'll write a letter to them. I can easily replicate on this > system, > although I don't know what is causing it. I'm guessing this product has > gone > through a ton of testing and this issue would have already been resolved? > I > don't know what to do. > > Considering I need to lower my firewalls on my clients for file sharing > (which seems weird) the only option I can see is to work with ISA server > which I've heard is a big headache in 2003 server but left with no other > options I don't think I have a choice. I can't leave my network wide > open, > that is for sure. > > "Jorge Silva" wrote: > >> Very strange.... >> >> DON'T REMOVE THE FIREWAL. >> >> I already setup several RRAS servers and they work fine, were did you >> enable >> the Basic Firewal (In the internal Interface or in the Public Interface)? >> >> -- >> I hope that the information above helps you >> >> Good Luck >> Jorge Silva >> MCSA >> Systems Administrator >> >> "Greg P" <gsp@newsgroups.nospam> wrote in message >> news:6E45E005-53B4-4674-9196-0198A6449A17@microsoft.com... >> > Jorge, >> > >> > It works!! and this has to be a bug!!! When configuring RRAS if I have >> > the >> > RRAS firewall enabled I have the problem, If i remove the basic >> > firewall >> > when >> > configuring RRAS it doesn't work. >> > >> > Why this only effect the two other computers and not my laptop makes no >> > sense to me, although there has to be a reason. But this has to be a >> > bug, >> > if >> > the firewall doesn't allow certain clients to receive the reply from >> > the >> > web >> > site, dont' you think? >> > >> > Thanks, >> > >> > "Jorge Silva" wrote: >> > >> >> Check if you have nay filters enabled on the RRAS server. >> >> >> >> -- >> >> I hope that the information above helps you >> >> >> >> Good Luck >> >> Jorge Silva >> >> MCSA >> >> Systems Administrator >> >> >> >> "Greg P" <gsp@newsgroups.nospam> wrote in message >> >> news:11E781ED-0DBA-41F7-86C7-63DDD5A9CB17@microsoft.com... >> >> > FYI I did ping my Gateway (the external nic on my server) and was >> >> > sucessful. >> >> > I realized you might need to know that. >> >> > >> >> > "Greg P" wrote: >> >> > >> >> >> Yes I am using Remote Access to access the internet. All of your >> >> >> suggustions >> >> >> worked (got a responce) and my trace gets out to MSN, but internet >> >> >> still >> >> >> doesn't work. 192..168.10.1 is my server 192.168.10.3 is my >> >> >> desktop >> >> >> (the >> >> >> one >> >> >> I ran the trace on, but can't use the internet on) below are my >> >> >> pings >> >> >> and >> >> >> trace. >> >> >> >> >> >> Microsoft Windows XP [Version 5.1.2600] >> >> >> (C) Copyright 1985-2001 Microsoft Corp. >> >> >> >> >> >> C:\Documents and Settings\gperrego>ping 127.0.0.1 >> >> >> >> >> >> Pinging 127.0.0.1 with 32 bytes of data: >> >> >> >> >> >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 >> >> >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 >> >> >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 >> >> >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 >> >> >> >> >> >> Ping statistics for 127.0.0.1: >> >> >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), >> >> >> Approximate round trip times in milli-seconds: >> >> >> Minimum = 0ms, Maximum = 0ms, Average = 0ms >> >> >> >> >> >> C:\Documents and Settings\gperrego>ping 192.168.10.1 >> >> >> >> >> >> Pinging 192.168.10.1 with 32 bytes of data: >> >> >> >> >> >> Reply from 192.168.10.1: bytes=32 time=101ms TTL=128 >> >> >> Reply from 192.168.10.1: bytes=32 time=174ms TTL=128 >> >> >> Reply from 192.168.10.1: bytes=32 time=1ms TTL=128 >> >> >> Reply from 192.168.10.1: bytes=32 time=1ms TTL=128 >> >> >> >> >> >> Ping statistics for 192.168.10.1: >> >> >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), >> >> >> Approximate round trip times in milli-seconds: >> >> >> Minimum = 1ms, Maximum = 174ms, Average = 69ms >> >> >> >> >> >> C:\Documents and Settings\gperrego>ping 192.168.10.3 >> >> >> >> >> >> Pinging 192.168.10.3 with 32 bytes of data: >> >> >> >> >> >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 >> >> >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 >> >> >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 >> >> >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 >> >> >> >> >> >> Ping statistics for 192.168.10.3: >> >> >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), >> >> >> Approximate round trip times in milli-seconds: >> >> >> Minimum = 0ms, Maximum = 0ms, Average = 0ms >> >> >> >> >> >> C:\Documents and Settings\gperrego>ping 192.168.10.2 >> >> >> >> >> >> Pinging 192.168.10.2 with 32 bytes of data: >> >> >> >> >> >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 >> >> >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 >> >> >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 >> >> >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 >> >> >> >> >> >> Ping statistics for 192.168.10.2: >> >> >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), >> >> >> Approximate round trip times in milli-seconds: >> >> >> Minimum = 0ms, Maximum = 0ms, Average = 0ms >> >> >> >> >> >> C:\Documents and Settings\gperrego>tracert www.microsoft.com >> >> >> >> >> >> Tracing route to lb1.www.ms.akadns.net [207.46.199.30] >> >> >> over a maximum of 30 hops: >> >> >> >> >> >> 1 1 ms 1 ms 1 ms nugget.sbs.net [192.168.10.1] >> >> >> 2 7 ms 8 ms 8 ms 10.37.160.1 >> >> >> 3 8 ms 8 ms 8 ms gig0-2.austtxa-ubr7.austin.rr.com >> >> >> [24.27.12.81] >> >> >> >> >> >> 4 9 ms 9 ms 7 ms gig2-3.austtxa-rtr1.austin.rr.com >> >> >> [24.27.12.85] >> >> >> >> >> >> 5 18 ms 10 ms 9 ms srp0-0.austtxrdc-rtr2.austin.rr.com >> >> >> [24.27.12.34 >> >> >> ] >> >> >> 6 9 ms 8 ms 9 ms pos1-0.austtxrdc-rtr4.texas.rr.com >> >> >> [66.68.1.110] >> >> >> >> >> >> 7 17 ms 18 ms 16 ms son0-0-0.hstqtxl3-rtr1.texas.rr.com >> >> >> [24.93.33.15 >> >> >> 3] >> >> >> 8 18 ms 17 ms 16 ms 4.79.88.21 >> >> >> 9 16 ms 16 ms 18 ms ge-2-0-0.mp1.Houston1.Level3.net >> >> >> [4.68.97.241] >> >> >> 10 172 ms 110 ms 60 ms as-1-0.mp2.Seattle1.Level3.net >> >> >> [209.247.10.133] >> >> >> >> >> >> 11 61 ms 61 ms 59 ms >> >> >> ge-2-0-0-52.gar1.Seattle1.Level3.net >> >> >> [4.68.105.4 >> >> >> 1] >> >> >> 12 60 ms 61 ms 62 ms 65.59.235.6 >> >> >> 13 94 ms 62 ms 62 ms 207.46.37.225 >> >> >> 14 62 ms 61 ms 63 ms pos1-0.tuk-12ix-1b.ntwk.msn.net >> >> >> [207.46.36.146] >> >> >> >> >> >> 15 60 ms 62 ms 62 ms pos1-0.tke-12ix-1b.ntwk.msn.net >> >> >> [207.46.155.5] >> >> >> 16 60 ms 60 ms 60 ms po10.tuk-65ns-mcs-1a.ntwk.msn.net >> >> >> [207.46.224.15 >> >> >> 1] >> >> >> 17 * ^C >> >> >> C:\Documents and Settings\gperrego> >> >> >> >> >> >> "Jorge Silva" wrote: >> >> >> >> >> >> > The request TimesOut -> normal, the servers in the internet won't >> >> >> > reply >> >> >> > to >> >> >> > ping requets because they are protected by firewalls. >> >> >> > >> >> >> > Basic Steps to troubleshoot are: >> >> >> > >> >> >> > 1. Ping the loopback address to verify that TCP/IP is installed >> >> >> > and >> >> >> > configured correctly on the local computer. To perform this step, >> >> >> > enter >> >> >> > ping >> >> >> > 127.0.0.1 at a command prompt. >> >> >> > >> >> >> > If the loopback step fails, the IP stack is not responding. This >> >> >> > problem >> >> >> > might be occurring because the TCP drivers are corrupted, the >> >> >> > network >> >> >> > adapter might not be working, or another service might be >> >> >> > interfering >> >> >> > with >> >> >> > IP. >> >> >> > >> >> >> > >> >> >> > >> >> >> > 2. Ping the IP address of the local computer to verify that an >> >> >> > address >> >> >> > has >> >> >> > been added correctly. To perform this step, enter ping <IP >> >> >> > address >> >> >> > of >> >> >> > local >> >> >> > host> at a command prompt. >> >> >> > >> >> >> > >> >> >> > >> >> >> > 3. Ping the IP address of the default gateway. This step verifies >> >> >> > that >> >> >> > the >> >> >> > default gateway is reachable and that the local host can >> >> >> > communicate >> >> >> > with >> >> >> > another host on the network. To perform this step, enter ping <IP >> >> >> > address of >> >> >> > default gateway> at a command prompt. >> >> >> > >> >> >> > >> >> >> > >> >> >> > Then you can use Tracert which is a route-tracing utility that >> >> >> > allows >> >> >> > you to >> >> >> > track the path of a forwarded packet from router to router for up >> >> >> > to >> >> >> > 30 >> >> >> > hops. Tracert works by sending ICMP echo requests to an IP >> >> >> > address, >> >> >> > while >> >> >> > incrementing the Time to Live (TTL) field in the IP header, >> >> >> > starting >> >> >> > at >> >> >> > 1, >> >> >> > and analyzing the ICMP errors that are returned. Tracert prints >> >> >> > out >> >> >> > an >> >> >> > ordered list of the routers in the path that returned these error >> >> >> > messages. >> >> >> > >> >> >> > >> >> >> > Type on command prompt: >> >> >> > <tracert www.microsoft.com> press enter >> >> >> > >> >> >> > >> >> >> > -- >> >> >> > I hope that the information above helps you >> >> >> > >> >> >> > Good Luck >> >> >> > Jorge Silva >> >> >> > MCSA >> >> >> > Systems Administrator >> >> >> > >> >> >> > "Greg P" <gsp@newsgroups.nospam> wrote in message >> >> >> > news:01B390CF-90D6-4305-9008-8E34BE2E69E6@microsoft.com... >> >> >> > > Jorge, >> >> >> > > >> >> >> > > I reset internet options to no avail. One thing i'm not sure >> >> >> > > about >> >> >> > > is >> >> >> > > when >> >> >> > > I ping the internet from any computer on the network the >> >> >> > > request >> >> >> > > times >> >> >> > > out. >> >> >> > > Even the server and the laptop that the internet works on. >> >> >> > > Otherwise >> >> >> > > I'm >> >> >> > > totally stumped. >> >> >> > > >> >> >> > > Thanks, >> >> >> > > Greg >> >> >> > > >> >> >> > > "Jorge Silva" wrote: >> >> >> > > >> >> >> > >> > I uninstalled Norton totally from the desktop. If it can't >> >> >> > >> > connect to >> >> >> > >> > the >> >> >> > >> > internet I can't get a virus :) >> >> >> > >> >> >> >> > >> It looks that your Dns resolution is working well. So the only >> >> >> > >> explanation >> >> >> > >> that I can remember at this moment is that there is something >> >> >> > >> or >> >> >> > >> some >> >> >> > >> filter >> >> >> > >> that prevents you from going to the internet. Check Internet >> >> >> > >> options >> >> >> > >> or >> >> >> > >> any >> >> >> > >> type of configuration internet related that you migh have in >> >> >> > >> your >> >> >> > >> pc. >> >> >> > >> -- >> >> >> > >> I hope that the information above helps you >> >> >> > >> >> >> >> > >> Good Luck >> >> >> > >> Jorge Silva >> >> >> > >> MCSA >> >> >> > >> Systems Administrator >> >> >> > >> >> >> >> > >> "Greg P" <gsp@newsgroups.nospam> wrote in message >> >> >> > >> news:3BDBCBA0-CDBF-4A47-8B91-B77978A81F49@microsoft.com... >> >> >> > >> > Jorge, >> >> >> > >> > >> >> >> > >> > Unfortunately I'm in the same spot that I started in, except >> >> >> > >> > we >> >> >> > >> > solved >> >> >> > >> > the >> >> >> > >> > file sharing issue on Laptop 2 by lowering the Norton >> >> >> > >> > firewall. >> >> >> > >> > I >> >> >> > >> > still >> >> >> > >> > can't access the internet on the desktop or laptop 2, even >> >> >> > >> > though I actually used that article to set up my NAT in the first place and another
written by the same author. I was able to reproduce until I unpluged my desktop and cycled it off of the network. Then plugged the rj-45 back in and it worked with the firewall enabled. I have no idea why that would solve this but it did. Jorge you have been a great help and i really appreciate you time. Time for me to move on to ISA. Thanks, Greg Show quoteHide quote "Jorge Silva" wrote: > Check if you have nay filters enabled on the RRAS server. > > -- > I hope that the information above helps you > > Good Luck > Jorge Silva > MCSA > Systems Administrator > > "Greg P" <gsp@newsgroups.nospam> wrote in message > news:11E781ED-0DBA-41F7-86C7-63DDD5A9CB17@microsoft.com... > > FYI I did ping my Gateway (the external nic on my server) and was > > sucessful. > > I realized you might need to know that. > > > > "Greg P" wrote: > > > >> Yes I am using Remote Access to access the internet. All of your > >> suggustions > >> worked (got a responce) and my trace gets out to MSN, but internet still > >> doesn't work. 192..168.10.1 is my server 192.168.10.3 is my desktop (the > >> one > >> I ran the trace on, but can't use the internet on) below are my pings and > >> trace. > >> > >> Microsoft Windows XP [Version 5.1.2600] > >> (C) Copyright 1985-2001 Microsoft Corp. > >> > >> C:\Documents and Settings\gperrego>ping 127.0.0.1 > >> > >> Pinging 127.0.0.1 with 32 bytes of data: > >> > >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > >> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 > >> > >> Ping statistics for 127.0.0.1: > >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > >> Approximate round trip times in milli-seconds: > >> Minimum = 0ms, Maximum = 0ms, Average = 0ms > >> > >> C:\Documents and Settings\gperrego>ping 192.168.10.1 > >> > >> Pinging 192.168.10.1 with 32 bytes of data: > >> > >> Reply from 192.168.10.1: bytes=32 time=101ms TTL=128 > >> Reply from 192.168.10.1: bytes=32 time=174ms TTL=128 > >> Reply from 192.168.10.1: bytes=32 time=1ms TTL=128 > >> Reply from 192.168.10.1: bytes=32 time=1ms TTL=128 > >> > >> Ping statistics for 192.168.10.1: > >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > >> Approximate round trip times in milli-seconds: > >> Minimum = 1ms, Maximum = 174ms, Average = 69ms > >> > >> C:\Documents and Settings\gperrego>ping 192.168.10.3 > >> > >> Pinging 192.168.10.3 with 32 bytes of data: > >> > >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 > >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 > >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 > >> Reply from 192.168.10.3: bytes=32 time<1ms TTL=128 > >> > >> Ping statistics for 192.168.10.3: > >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > >> Approximate round trip times in milli-seconds: > >> Minimum = 0ms, Maximum = 0ms, Average = 0ms > >> > >> C:\Documents and Settings\gperrego>ping 192.168.10.2 > >> > >> Pinging 192.168.10.2 with 32 bytes of data: > >> > >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 > >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 > >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 > >> Reply from 192.168.10.2: bytes=32 time<1ms TTL=128 > >> > >> Ping statistics for 192.168.10.2: > >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > >> Approximate round trip times in milli-seconds: > >> Minimum = 0ms, Maximum = 0ms, Average = 0ms > >> > >> C:\Documents and Settings\gperrego>tracert www.microsoft.com > >> > >> Tracing route to lb1.www.ms.akadns.net [207.46.199.30] > >> over a maximum of 30 hops: > >> > >> 1 1 ms 1 ms 1 ms nugget.sbs.net [192.168.10.1] > >> 2 7 ms 8 ms 8 ms 10.37.160.1 > >> 3 8 ms 8 ms 8 ms gig0-2.austtxa-ubr7.austin.rr.com > >> [24.27.12.81] > >> > >> 4 9 ms 9 ms 7 ms gig2-3.austtxa-rtr1.austin.rr.com > >> [24.27.12.85] > >> > >> 5 18 ms 10 ms 9 ms srp0-0.austtxrdc-rtr2.austin.rr.com > >> [24.27.12.34 > >> ] > >> 6 9 ms 8 ms 9 ms pos1-0.austtxrdc-rtr4.texas.rr.com > >> [66.68.1.110] > >> > >> 7 17 ms 18 ms 16 ms son0-0-0.hstqtxl3-rtr1.texas.rr.com > >> [24.93.33.15 > >> 3] > >> 8 18 ms 17 ms 16 ms 4.79.88.21 > >> 9 16 ms 16 ms 18 ms ge-2-0-0.mp1.Houston1.Level3.net > >> [4.68.97.241] > >> 10 172 ms 110 ms 60 ms as-1-0.mp2.Seattle1.Level3.net > >> [209.247.10.133] > >> > >> 11 61 ms 61 ms 59 ms ge-2-0-0-52.gar1.Seattle1.Level3.net > >> [4.68.105.4 > >> 1] > >> 12 60 ms 61 ms 62 ms 65.59.235.6 > >> 13 94 ms 62 ms 62 ms 207.46.37.225 > >> 14 62 ms 61 ms 63 ms pos1-0.tuk-12ix-1b.ntwk.msn.net > >> [207.46.36.146] > >> > >> 15 60 ms 62 ms 62 ms pos1-0.tke-12ix-1b.ntwk.msn.net > >> [207.46.155.5] > >> 16 60 ms 60 ms 60 ms po10.tuk-65ns-mcs-1a.ntwk.msn.net > >> [207.46.224.15 > >> 1] > >> 17 * ^C > >> C:\Documents and Settings\gperrego> > >> > >> "Jorge Silva" wrote: > >> > >> > The request TimesOut -> normal, the servers in the internet won't reply > >> > to > >> > ping requets because they are protected by firewalls. > >> > > >> > Basic Steps to troubleshoot are: > >> > > >> > 1. Ping the loopback address to verify that TCP/IP is installed and > >> > configured correctly on the local computer. To perform this step, enter > >> > ping > >> > 127.0.0.1 at a command prompt. > >> > > >> > If the loopback step fails, the IP stack is not responding. This > >> > problem > >> > might be occurring because the TCP drivers are corrupted, the network > >> > adapter might not be working, or another service might be interfering > >> > with > >> > IP. > >> > > >> > > >> > > >> > 2. Ping the IP address of the local computer to verify that an address > >> > has > >> > been added correctly. To perform this step, enter ping <IP address of > >> > local > >> > host> at a command prompt. > >> > > >> > > >> > > >> > 3. Ping the IP address of the default gateway. This step verifies that > >> > the > >> > default gateway is reachable and that the local host can communicate > >> > with > >> > another host on the network. To perform this step, enter ping <IP > >> > address of > >> > default gateway> at a command prompt. > >> > > >> > > >> > > >> > Then you can use Tracert which is a route-tracing utility that allows > >> > you to > >> > track the path of a forwarded packet from router to router for up to 30 > >> > hops. Tracert works by sending ICMP echo requests to an IP address, > >> > while > >> > incrementing the Time to Live (TTL) field in the IP header, starting at > >> > 1, > >> > and analyzing the ICMP errors that are returned. Tracert prints out an > >> > ordered list of the routers in the path that returned these error > >> > messages. > >> > > >> > > >> > Type on command prompt: > >> > <tracert www.microsoft.com> press enter > >> > > >> > > >> > -- > >> > I hope that the information above helps you > >> > > >> > Good Luck > >> > Jorge Silva > >> > MCSA > >> > Systems Administrator > >> > > >> > "Greg P" <gsp@newsgroups.nospam> wrote in message > >> > news:01B390CF-90D6-4305-9008-8E34BE2E69E6@microsoft.com... > >> > > Jorge, > >> > > > >> > > I reset internet options to no avail. One thing i'm not sure about > >> > > is > >> > > when > >> > > I ping the internet from any computer on the network the request > >> > > times > >> > > out. > >> > > Even the server and the laptop that the internet works on. Otherwise > >> > > I'm > >> > > totally stumped. > >> > > > >> > > Thanks, > >> > > Greg > >> > > > >> > > "Jorge Silva" wrote: > >> > > > >> > >> > I uninstalled Norton totally from the desktop. If it can't > >> > >> > connect to > >> > >> > the > >> > >> > internet I can't get a virus :) > >> > >> > >> > >> It looks that your Dns resolution is working well. So the only > >> > >> explanation > >> > >> that I can remember at this moment is that there is something or > >> > >> some > >> > >> filter > >> > >> that prevents you from going to the internet. Check Internet options > >> > >> or > >> > >> any > >> > >> type of configuration internet related that you migh have in your > >> > >> pc. > >> > >> -- > >> > >> I hope that the information above helps you > >> > >> > >> > >> Good Luck > >> > >> Jorge Silva > >> > >> MCSA > >> > >> Systems Administrator > >> > >> > >> > >> "Greg P" <gsp@newsgroups.nospam> wrote in message > >> > >> news:3BDBCBA0-CDBF-4A47-8B91-B77978A81F49@microsoft.com... > >> > >> > Jorge, > >> > >> > > >> > >> > Unfortunately I'm in the same spot that I started in, except we > >> > >> > solved > >> > >> > the > >> > >> > file sharing issue on Laptop 2 by lowering the Norton firewall. I > >> > >> > still > >> > >> > can't access the internet on the desktop or laptop 2, even though > >> > >> > they > >> > >> > are > >> > >> > on > >> > >> > the dame domain as Laptop 1 which can access the internet. With > >> > >> > that > >> > >> > being > >> > >> > said I'm not sure if you still think this is a DNS problem? > >> > >> > > >> > >> >>Well you said that now you have everything working except > >> > >> >>Internet, and > >> > >> >>you also said that you don't have Proxy or any other thing that > >> > >> > prevents/restricts users to access to the internet, so you must > >> > >> > have a > >> > >> > DNS > >> > >> > resolution problem. > >> > >> > > >> > >> >>Do you have Forwarding enabled in the Dns server? > >> > >> > > >> > >> > Yes, this is set up with the correct ip addresses. > >> > >> > > >> > >> >>Test the resolution on the DC - Go to command prompt and type ping > >> > >> >>www.microsoft.com - check if returns the Ipaddress of the site > >> > >> > then go to the clients and check if the ping command returns the > >> > >> > Ipaddress > >> > >> > of the site. > >> > >> > > >> > >> > All resolve the IP address, all requests time out. > >> > >> > > >> > >> >>Right click on it and choose properties then you should have the > >> > >> >>"File > >> > >> >>and > >> > >> >>Print Sharing for Microsoft Networks Selected"; however you should > >> > >> >>disable/deselect this on the Public Interface (Security purposes). > >> > >> > > >> > >> > The File and Print Sharing was selected previously. (there wasn't > >> > >> > a > >> > >> > Public > >> > >> > Interface option for this nic, there are only 4 options in the > >> > >> > properties > >> > >> > page, Client for MS Networks, Network Lad Balancing, File and > >> > >> > Printer > >> > >> > Sharing, and TCP/IP) > >> > >> > > >> > >> >>Check also if is preventing Internet access or any other access to > >> > >> >>server > >> > >> >>or Dns, etc. Best practices here are for test DISABLE the Norton > >> > >> >>Firewall > >> > >> >>and test, in this way you can immediately check if this as > >> > >> >>relation > >> > >> >>with > >> > >> >>your current problems. > >> > >> > > >> > >> > I uninstalled Norton totally from the desktop. If it can't > >> > >> > connect to > >> > >> > the You are using RRAS to provide internet access right?
-- Show quoteHide quoteI hope that the information above helps you Good Luck Jorge Silva MCSA Systems Administrator "Greg P" <gsp@newsgroups.nospam> wrote in message news:01B390CF-90D6-4305-9008-8E34BE2E69E6@microsoft.com... > Jorge, > > I reset internet options to no avail. One thing i'm not sure about is > when > I ping the internet from any computer on the network the request times > out. > Even the server and the laptop that the internet works on. Otherwise I'm > totally stumped. > > Thanks, > Greg > > "Jorge Silva" wrote: > >> > I uninstalled Norton totally from the desktop. If it can't connect to >> > the >> > internet I can't get a virus :) >> >> It looks that your Dns resolution is working well. So the only >> explanation >> that I can remember at this moment is that there is something or some >> filter >> that prevents you from going to the internet. Check Internet options or >> any >> type of configuration internet related that you migh have in your pc. >> -- >> I hope that the information above helps you >> >> Good Luck >> Jorge Silva >> MCSA >> Systems Administrator >> >> "Greg P" <gsp@newsgroups.nospam> wrote in message >> news:3BDBCBA0-CDBF-4A47-8B91-B77978A81F49@microsoft.com... >> > Jorge, >> > >> > Unfortunately I'm in the same spot that I started in, except we solved >> > the >> > file sharing issue on Laptop 2 by lowering the Norton firewall. I >> > still >> > can't access the internet on the desktop or laptop 2, even though they >> > are >> > on >> > the dame domain as Laptop 1 which can access the internet. With that >> > being >> > said I'm not sure if you still think this is a DNS problem? >> > >> >>Well you said that now you have everything working except Internet, and >> >>you also said that you don't have Proxy or any other thing that >> > prevents/restricts users to access to the internet, so you must have a >> > DNS >> > resolution problem. >> > >> >>Do you have Forwarding enabled in the Dns server? >> > >> > Yes, this is set up with the correct ip addresses. >> > >> >>Test the resolution on the DC - Go to command prompt and type ping >> >>www.microsoft.com - check if returns the Ipaddress of the site >> > then go to the clients and check if the ping command returns the >> > Ipaddress >> > of the site. >> > >> > All resolve the IP address, all requests time out. >> > >> >>Right click on it and choose properties then you should have the "File >> >>and >> >>Print Sharing for Microsoft Networks Selected"; however you should >> >>disable/deselect this on the Public Interface (Security purposes). >> > >> > The File and Print Sharing was selected previously. (there wasn't a >> > Public >> > Interface option for this nic, there are only 4 options in the >> > properties >> > page, Client for MS Networks, Network Lad Balancing, File and Printer >> > Sharing, and TCP/IP) >> > >> >>Check also if is preventing Internet access or any other access to >> >>server >> >>or Dns, etc. Best practices here are for test DISABLE the Norton >> >>Firewall >> >>and test, in this way you can immediately check if this as relation >> >>with >> >>your current problems. >> > >> > I uninstalled Norton totally from the desktop. If it can't connect to >> > the >> > internet I can't get a virus :) >> > >> > >> > "Jorge Silva" wrote: >> > >> >> In line >> >> >> >> >> >> >> >> > What is a multihomed DC? >> >> >> >> >> >> >> >> Is a Domain controller with more than one Nic (Network Interface Card) >> >> card >> >> >> >> >> >> >> >> > What do I need to change on my server to mave this work? >> >> >> >> >> >> >> >> Well you said that now you have everything working except Internet, >> >> and >> >> you >> >> also said that you don't have Proxy or any other thing that >> >> prevents/restricts users to access to the internet, so you must have a >> >> DNS >> >> resolution problem. >> >> >> >> >> >> >> >> - Do you have Forwarding enabled in the Dns server? If no go to the >> >> Dns >> >> console -> right click Dns server choose properties -> select >> >> forwarders >> >> tab -> Select All other Domains -> got to the Selected domain's >> >> forwarder >> >> Ipaddress list and place the ISP Dns server address -> click add -> >> >> restart >> >> Dns service. >> >> >> >> >> >> >> >> Test the resolution on the DC - Go to command prompt and type ping >> >> www.microsoft.com - check if returns the Ipaddress of the site, then >> >> go >> >> to >> >> the clients and check if the ping command returns the Ipaddress of the >> >> site. >> >> >> >> >> >> >> >> > Are you saying I shouldn't have WINS and DNS on the same computer? >> >> >> >> >> >> >> >> No. What I said was in a Multihomed DC you could have problems with >> >> Wins >> >> and >> >> Dns. >> >> >> >> >> >> > FYI I uninstalled WINS and see the same problem, do I need to >> >> > remove >> >> > some >> >> > records somewhere? >> >> >> >> >> >> >> >> You'll only need WINS if you're using any APP in your network that >> >> needs >> >> NetBIOS resolution or if you have the need to browse over different >> >> subnets >> >> using for example Network Places. >> >> >> >> >> >> >> >> > As for configuring the DNS as you said I already had the interfaces >> >> > set >> >> > to >> >> > only use the local Nic. >> >> >> >> >> >> >> >> - Great >> >> >> >> >> >> > As for setting the binding order the internal Nic was at the top of >> >> > the >> >> > list. How do I check to see if file sharing is only on that NIC? >> >> >> >> >> >> >> >> - Right click on it and choose properties then you should have the >> >> "File >> >> and >> >> Print Sharing for Microsoft Networks Selected"; however you should >> >> disable/deselect this on the Public Interface (Security purposes). >> >> >> >> >> >> > I had lowered the windows firewall but there was a Norton Firewall >> >> > that >> >> > was >> >> > preventing Laptop 2 from Filesharing. That now works. So both the >> >> > desktop >> >> > and Laptop 2 have the same issues. They get an IP, can perform >> >> > Fielsharing >> >> > but can't connect to the internet. >> >> >> >> >> >> >> >> Check also if is preventing Internet access or any other access to >> >> server >> >> or >> >> Dns, etc. Best practices here are for test DISABLE the Norton Firewall >> >> and >> >> test, in this way you can immediately check if this as relation with >> >> your >> >> current problems. >> >> >> >> >> >> >> >> -- >> >> I hope that the information above helps you >> >> >> >> Good Luck >> >> Jorge Silva >> >> MCSA >> >> Systems Administrator >> >> >> >> "Greg P" <gsp@newsgroups.nospam> wrote in message >> >> news:25530004-70F9-484D-A87A-26A6B823685F@microsoft.com... >> >> > Jorge, >> >> > >> >> > What is a multihomed DC? What do I need to change on my server to >> >> > mave >> >> > this >> >> > work? Are you saying I shouldn't have WINS and DNS on the same >> >> > computer? >> >> > FYI I uninstalled WINS and see the same problem, do I need to >> >> > remove >> >> > some >> >> > records somewhere? >> >> > >> >> > As for configuring the DNS as you said I already had the interfaces >> >> > set >> >> > to >> >> > only use the local nic. >> >> > >> >> > As for setting the binding order the internal nic was at the top of >> >> > the >> >> > list. How do I check to see if file sharing is only on that NIC? >> >> > >> >> > I had lowered the windows firewall but there was a Norton Firewall >> >> > that >> >> > was >> >> > preventing Laptop 2 from Filesharing. That now works. So both the >> >> > desktop >> >> > and Laptop 2 have the same issues. They get an IP, can perform >> >> > Fielsharing >> >> > but can't connect to the internet. >> >> > >> >> > Thanks, >> >> > Greg >> >> > >> >> > "Jorge Silva" wrote: >> >> > >> >> >> >> >> >> - You shouldn't have a multihomed DC. >> >> >> check: >> >> >> >> >> >> Also, make sure the internal adapter is at the top of the binding >> >> >> order >> >> >> and >> >> >> that File Sharing is only bound on the internal adapter. >> >> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;266771 >> >> >> >> >> >> Active Directory communication fails on multihomed domain >> >> >> controllers >> >> >> >> >> >> http://support.microsoft.com/?id=272294 >> >> >> >> >> >> Name resolution and connectivity issues on a Routing and Remote >> >> >> Access >> >> >> Server that also runs DNS or WINS >> >> >> >> >> >> http://support.microsoft.com/kb/292822 >> >> >> >> >> >> >> >> >> - If the machines are running SP2 you need to open the FW to File >> >> >> share >> >> >> access. >> >> >> - Configure the Dns server to listen only on internal adpter (Open >> >> >> Dns >> >> >> server mmc console -> Right click on Dns server -> choose >> >> >> properties -> >> >> >> goto >> >> >> interfaces tab -> choose only the following IP Addresses, and make >> >> >> sure >> >> >> that >> >> >> you only have the internal interface there) >> >> >> >> >> >> >> >> >> -- >> >> >> I hope that the information above helps you >> >> >> >> >> >> Good Luck >> >> >> Jorge Silva >> >> >> MCSA >> >> >> Systems Administrator >> >> >> >> >> >> "Greg P" <gsp@newsgroups.nospam> wrote in message >> >> >> news:D1DAA442-DF0E-42DC-9725-02A55AFEF4AB@microsoft.com... >> >> >> > Each client machine is running Win XP Pro. >> >> >> > >> >> >> > No Proxy devices. >> >> >> > >> >> >> > I can access the internet from the server. >> >> >> > >> >> >> > Ipconfig on all 4 machines: >> >> >> > >> >> >> > Win 2003 Server >> >> >> > >> >> >> > Windows IP Configuration >> >> >> > >> >> >> > Host Name . . . . . . . . . . . . : Nugget >> >> >> > Primary Dns Suffix . . . . . . . : sbs.net >> >> >> > Node Type . . . . . . . . . . . . : Unknown >> >> >> > IP Routing Enabled. . . . . . . . : Yes >> >> >> > WINS Proxy Enabled. . . . . . . . : Yes >> >> >> > DNS Suffix Search List. . . . . . : sbs.net >> >> >> > austin.rr.com >> >> >> > >> >> >> > Ethernet adapter Local Area Connection: >> >> >> > >> >> >> > Connection-specific DNS Suffix . : austin.rr.com >> >> >> > Description . . . . . . . . . . . : NVIDIA nForce Networking >> >> >> > Controller >> >> >> > Physical Address. . . . . . . . . : 00-XX-8D-DB-16-XX >> >> >> > DHCP Enabled. . . . . . . . . . . : Yes >> >> >> > Autoconfiguration Enabled . . . . : Yes >> >> >> > IP Address. . . . . . . . . . . . : xxx.112.216.xxx >> >> >> > Subnet Mask . . . . . . . . . . . : 255.255.240.0 >> >> >> > Default Gateway . . . . . . . . . : 70.112.208.1 >> >> >> > DHCP Server . . . . . . . . . . . : 10.37.160.1 >> >> >> > DNS Servers . . . . . . . . . . . : 24.93.40.62 >> >> >> > 24.93.40.63 >> >> >> > 24.93.40.75 >> >> >> > Lease Obtained. . . . . . . . . . : Thursday, June 08, 2006 >> >> >> > 11:20:40 >> >> >> > AM >> >> >> > Lease Expires . . . . . . . . . . : Thursday, June 08, 2006 >> >> >> > 1:20:40 >> >> >> > PM >> >> >> > >> >> >> > Ethernet adapter Local Area Connection 2: >> >> >> > >> >> >> > Connection-specific DNS Suffix . : >> >> >> > Description . . . . . . . . . . . : D-Link DFE-530TX+ PCI Fast >> >> >> > Ethernet >> >> >> > Adapt >> >> >> > er (rev.F) What is the subnet, mask and gateway definition for the pool? From your
gateway machine can you get to the internet? Does dns on the clients point to the AD dns server? Does the AD DNS server forward DNS requests it doesn't know or does it handle all dns traffic? Can your DNS server get to the internet? As you can see you need to provide finally detailed answers. There just isn;t enought info provided to help you pin it down. -- Show quoteHide quotePaul Bergson MCT, MCSE, MCSA, Security+, CNE, CNA, CCA http://www.pbbergs.com Please no e-mails, any questions should be posted in the NewsGroup This posting is provided "AS IS" with no warranties, and confers no rights. "Greg P" <gsp@newsgroups.nospam> wrote in message news:DB62152E-EB19-479A-A791-A1B9C258023A@microsoft.com... > FYI: this is a double post because I want' sure which forum is was the > correct place to post this question. I have also posted on the technet > windows server general newsgroup but I think this is a better forum. > > I have a 2003 Server Running as DHCP and DNS, I have 3 cleint computers. > After adding each computer to the network I see 3 different result on each > computer. I am using a 2 NIC setup and I have a switch after the server. I > plan on using wireless but I see the same result with everything hard > wired > so lets stick with that. I have a 4 port switch that hard wires each > computer. > > Laptop 1 - Works as expected, 1) gets IP address 2) can see the other > computers on the network thorugh Windows Explorer and perform fileshare > fine > 3) Connects to the internet correctly. > > Desktop 1 - Doens't work 1) gets IP Address 2) can see the other computers > on the network thorugh Windows Explorer and fileshare fine 3) NO INTERNET > CONNECTION? > > Laptop 2 - Doesn't work 1) Gets IP Address 2) CAN'T SEE OTHER COMPUTERS OR > FILESHARE, BUT I CAN PING THEM? 3) NO INTERNET CONNECTION > > I have tried many things. I can unplug the cable from laptop 1 and place > into either desktop 1 or laptop 2 and s/ same results. I can uplug cable > from Either of the non working computers and they both work in Laptop 1. > So > that makes me think this has nothing to do with the hardware. > > I'm not sure what else to tell you about, I can see Laptop 2 from the 3 > Computers but can't actually open it up, but it does show up on the list > of > for the Domain in win explorer. > > As for the TCP/IP settings everything is exactly the same on each client > computer. > > In the Computers area of Active Directory everything is the same for all > three computers. > > Just to try it out I set up reserved leases for each NIC they work fine, > each computer signs on and gets the resevered IP Address. > > I have no idea where to go from here, please help. > > Thanks in advance, Ipconfigs are posted above, I think that answers you first question.
My gateway and DNS machine are the same machine, just one server. Yes I can access the internet from the server. I think the fact that I can ping the AD DNS server from all computers using the computer name says that it does point to the AD DNS Server but if not how do I test this? Not sure how to test if "Does the AD DNS server forward DNS requests it doesn't know or does it handle all dns traffic"? Thanks Greg Show quoteHide quote "Paul Bergson" wrote: > What is the subnet, mask and gateway definition for the pool? From your > gateway machine can you get to the internet? Does dns on the clients point > to the AD dns server? Does the AD DNS server forward DNS requests it > doesn't know or does it handle all dns traffic? Can your DNS server get to > the internet? > > As you can see you need to provide finally detailed answers. There just > isn;t enought info provided to help you pin it down. > > -- > Paul Bergson MCT, MCSE, MCSA, Security+, CNE, CNA, CCA > http://www.pbbergs.com > > Please no e-mails, any questions should be posted in the NewsGroup > > This posting is provided "AS IS" with no warranties, and confers no rights. > > "Greg P" <gsp@newsgroups.nospam> wrote in message > news:DB62152E-EB19-479A-A791-A1B9C258023A@microsoft.com... > > FYI: this is a double post because I want' sure which forum is was the > > correct place to post this question. I have also posted on the technet > > windows server general newsgroup but I think this is a better forum. > > > > I have a 2003 Server Running as DHCP and DNS, I have 3 cleint computers. > > After adding each computer to the network I see 3 different result on each > > computer. I am using a 2 NIC setup and I have a switch after the server. I > > plan on using wireless but I see the same result with everything hard > > wired > > so lets stick with that. I have a 4 port switch that hard wires each > > computer. > > > > Laptop 1 - Works as expected, 1) gets IP address 2) can see the other > > computers on the network thorugh Windows Explorer and perform fileshare > > fine > > 3) Connects to the internet correctly. > > > > Desktop 1 - Doens't work 1) gets IP Address 2) can see the other computers > > on the network thorugh Windows Explorer and fileshare fine 3) NO INTERNET > > CONNECTION? > > > > Laptop 2 - Doesn't work 1) Gets IP Address 2) CAN'T SEE OTHER COMPUTERS OR > > FILESHARE, BUT I CAN PING THEM? 3) NO INTERNET CONNECTION > > > > I have tried many things. I can unplug the cable from laptop 1 and place > > into either desktop 1 or laptop 2 and s/ same results. I can uplug cable > > from Either of the non working computers and they both work in Laptop 1. > > So > > that makes me think this has nothing to do with the hardware. > > > > I'm not sure what else to tell you about, I can see Laptop 2 from the 3 > > Computers but can't actually open it up, but it does show up on the list > > of > > for the Domain in win explorer. > > > > As for the TCP/IP settings everything is exactly the same on each client > > computer. > > > > In the Computers area of Active Directory everything is the same for all > > three computers. > > > > Just to try it out I set up reserved leases for each NIC they work fine, > > each computer signs on and gets the resevered IP Address. > > > > I have no idea where to go from here, please help. > > > > Thanks in advance, > > > 
Other interesting topics
adprep.exe /forestprep R2 on 2003 domain fails
Problem with DC Configuration Container Moving DC`s to other OU`s use of .local domain for remote site vs rea domain name group policy question on workstation and terminal server for same How to Rename and Address computers in a AD domain How to remove individual ACEs from ADAM directory object Need to input the account and password when access "\\DC\netlogon" How many users are connected to AD |
|||||||||||||||||||||||
