If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#61
|
|||
|
|||
Network Setup Wizard
On Thu, 22 Jul 2004 21:21:55 -0400, "Doug Sherman [MVP]"
wrote: 2. Highlight TCP/IP and click the Properties button. Click the Advanced button and select the WINS tab. Either Default or Enable NetBIOS should be selected. If Disable NetBIOS was selected, that is the problem. Can you explain why it's the problem, please.? I know it resolved his problem, but I thought netbios was only required if the LAN contained win9x, winme or winnt machines. As both his machines are winxp, shouldn't they have been able to share files via port 445 using smb directly over tcp/ip without the need for netbios? Jim. |
Ads |
#62
|
|||
|
|||
Network Setup Wizard
On Thu, 22 Jul 2004 21:21:55 -0400, "Doug Sherman [MVP]"
wrote: 2. Highlight TCP/IP and click the Properties button. Click the Advanced button and select the WINS tab. Either Default or Enable NetBIOS should be selected. If Disable NetBIOS was selected, that is the problem. Can you explain why it's the problem, please.? I know it resolved his problem, but I thought netbios was only required if the LAN contained win9x, winme or winnt machines. As both his machines are winxp, shouldn't they have been able to share files via port 445 using smb directly over tcp/ip without the need for netbios? Jim. |
#63
|
|||
|
|||
Network Setup Wizard
On Thu, 22 Jul 2004 21:21:55 -0400, "Doug Sherman [MVP]"
wrote: 2. Highlight TCP/IP and click the Properties button. Click the Advanced button and select the WINS tab. Either Default or Enable NetBIOS should be selected. If Disable NetBIOS was selected, that is the problem. Can you explain why it's the problem, please.? I know it resolved his problem, but I thought netbios was only required if the LAN contained win9x, winme or winnt machines. As both his machines are winxp, shouldn't they have been able to share files via port 445 using smb directly over tcp/ip without the need for netbios? Jim. |
#64
|
|||
|
|||
Network Setup Wizard
On Thu, 22 Jul 2004 21:21:55 -0400, "Doug Sherman [MVP]"
wrote: 2. Highlight TCP/IP and click the Properties button. Click the Advanced button and select the WINS tab. Either Default or Enable NetBIOS should be selected. If Disable NetBIOS was selected, that is the problem. Can you explain why it's the problem, please.? I know it resolved his problem, but I thought netbios was only required if the LAN contained win9x, winme or winnt machines. As both his machines are winxp, shouldn't they have been able to share files via port 445 using smb directly over tcp/ip without the need for netbios? Jim. |
#65
|
|||
|
|||
Network Setup Wizard
On Thu, 22 Jul 2004 21:21:55 -0400, "Doug Sherman [MVP]"
wrote: 2. Highlight TCP/IP and click the Properties button. Click the Advanced button and select the WINS tab. Either Default or Enable NetBIOS should be selected. If Disable NetBIOS was selected, that is the problem. Can you explain why it's the problem, please.? I know it resolved his problem, but I thought netbios was only required if the LAN contained win9x, winme or winnt machines. As both his machines are winxp, shouldn't they have been able to share files via port 445 using smb directly over tcp/ip without the need for netbios? Jim. |
#66
|
|||
|
|||
Network Setup Wizard
There are 3 related, but separate issues involved:
1. File Sharing: Craig was able to share files and he successfully did so without NetBIOS by connecting to the IP address of the machine. 2. Name Resolution: In order to connect to or share files with a computer by using its name, there must be some mechanism in place on the network which translates names into IP addresses. In a properly configured Active Directory domain environment all machines will have a local DNS server available, so computer names can be resolved to IP addresses regardless of whether NetBIOS is enabled. In a peer to peer environment without a local DNS server (you could install one if you wanted to), you can use NetBIOS broadcasts to resolve computer names to IP addresses. If you don't have DNS and you don't have NetBIOS, you could use a hosts file - but if you don't have that either, then there is no way for computers to find each other by name. 3. Browsing: Browsing requires NetBIOS period. Even if computers exclusively use DNS or hosts files to resolve computer names to IP addresses, they will not be able to browse (My Network Places, Windows Explorer, etc.) unless NetBIOS is enabled. Doug Sherman MCSE Win2k/NT4.0, MCSA, MCP+I, MVP "James Egan" wrote in message ... On Thu, 22 Jul 2004 21:21:55 -0400, "Doug Sherman [MVP]" wrote: 2. Highlight TCP/IP and click the Properties button. Click the Advanced button and select the WINS tab. Either Default or Enable NetBIOS should be selected. If Disable NetBIOS was selected, that is the problem. Can you explain why it's the problem, please.? I know it resolved his problem, but I thought netbios was only required if the LAN contained win9x, winme or winnt machines. As both his machines are winxp, shouldn't they have been able to share files via port 445 using smb directly over tcp/ip without the need for netbios? Jim. |
#67
|
|||
|
|||
Network Setup Wizard
There are 3 related, but separate issues involved:
1. File Sharing: Craig was able to share files and he successfully did so without NetBIOS by connecting to the IP address of the machine. 2. Name Resolution: In order to connect to or share files with a computer by using its name, there must be some mechanism in place on the network which translates names into IP addresses. In a properly configured Active Directory domain environment all machines will have a local DNS server available, so computer names can be resolved to IP addresses regardless of whether NetBIOS is enabled. In a peer to peer environment without a local DNS server (you could install one if you wanted to), you can use NetBIOS broadcasts to resolve computer names to IP addresses. If you don't have DNS and you don't have NetBIOS, you could use a hosts file - but if you don't have that either, then there is no way for computers to find each other by name. 3. Browsing: Browsing requires NetBIOS period. Even if computers exclusively use DNS or hosts files to resolve computer names to IP addresses, they will not be able to browse (My Network Places, Windows Explorer, etc.) unless NetBIOS is enabled. Doug Sherman MCSE Win2k/NT4.0, MCSA, MCP+I, MVP "James Egan" wrote in message ... On Thu, 22 Jul 2004 21:21:55 -0400, "Doug Sherman [MVP]" wrote: 2. Highlight TCP/IP and click the Properties button. Click the Advanced button and select the WINS tab. Either Default or Enable NetBIOS should be selected. If Disable NetBIOS was selected, that is the problem. Can you explain why it's the problem, please.? I know it resolved his problem, but I thought netbios was only required if the LAN contained win9x, winme or winnt machines. As both his machines are winxp, shouldn't they have been able to share files via port 445 using smb directly over tcp/ip without the need for netbios? Jim. |
#68
|
|||
|
|||
Network Setup Wizard
There are 3 related, but separate issues involved:
1. File Sharing: Craig was able to share files and he successfully did so without NetBIOS by connecting to the IP address of the machine. 2. Name Resolution: In order to connect to or share files with a computer by using its name, there must be some mechanism in place on the network which translates names into IP addresses. In a properly configured Active Directory domain environment all machines will have a local DNS server available, so computer names can be resolved to IP addresses regardless of whether NetBIOS is enabled. In a peer to peer environment without a local DNS server (you could install one if you wanted to), you can use NetBIOS broadcasts to resolve computer names to IP addresses. If you don't have DNS and you don't have NetBIOS, you could use a hosts file - but if you don't have that either, then there is no way for computers to find each other by name. 3. Browsing: Browsing requires NetBIOS period. Even if computers exclusively use DNS or hosts files to resolve computer names to IP addresses, they will not be able to browse (My Network Places, Windows Explorer, etc.) unless NetBIOS is enabled. Doug Sherman MCSE Win2k/NT4.0, MCSA, MCP+I, MVP "James Egan" wrote in message ... On Thu, 22 Jul 2004 21:21:55 -0400, "Doug Sherman [MVP]" wrote: 2. Highlight TCP/IP and click the Properties button. Click the Advanced button and select the WINS tab. Either Default or Enable NetBIOS should be selected. If Disable NetBIOS was selected, that is the problem. Can you explain why it's the problem, please.? I know it resolved his problem, but I thought netbios was only required if the LAN contained win9x, winme or winnt machines. As both his machines are winxp, shouldn't they have been able to share files via port 445 using smb directly over tcp/ip without the need for netbios? Jim. |
#69
|
|||
|
|||
Network Setup Wizard
There are 3 related, but separate issues involved:
1. File Sharing: Craig was able to share files and he successfully did so without NetBIOS by connecting to the IP address of the machine. 2. Name Resolution: In order to connect to or share files with a computer by using its name, there must be some mechanism in place on the network which translates names into IP addresses. In a properly configured Active Directory domain environment all machines will have a local DNS server available, so computer names can be resolved to IP addresses regardless of whether NetBIOS is enabled. In a peer to peer environment without a local DNS server (you could install one if you wanted to), you can use NetBIOS broadcasts to resolve computer names to IP addresses. If you don't have DNS and you don't have NetBIOS, you could use a hosts file - but if you don't have that either, then there is no way for computers to find each other by name. 3. Browsing: Browsing requires NetBIOS period. Even if computers exclusively use DNS or hosts files to resolve computer names to IP addresses, they will not be able to browse (My Network Places, Windows Explorer, etc.) unless NetBIOS is enabled. Doug Sherman MCSE Win2k/NT4.0, MCSA, MCP+I, MVP "James Egan" wrote in message ... On Thu, 22 Jul 2004 21:21:55 -0400, "Doug Sherman [MVP]" wrote: 2. Highlight TCP/IP and click the Properties button. Click the Advanced button and select the WINS tab. Either Default or Enable NetBIOS should be selected. If Disable NetBIOS was selected, that is the problem. Can you explain why it's the problem, please.? I know it resolved his problem, but I thought netbios was only required if the LAN contained win9x, winme or winnt machines. As both his machines are winxp, shouldn't they have been able to share files via port 445 using smb directly over tcp/ip without the need for netbios? Jim. |
#70
|
|||
|
|||
Network Setup Wizard
There are 3 related, but separate issues involved:
1. File Sharing: Craig was able to share files and he successfully did so without NetBIOS by connecting to the IP address of the machine. 2. Name Resolution: In order to connect to or share files with a computer by using its name, there must be some mechanism in place on the network which translates names into IP addresses. In a properly configured Active Directory domain environment all machines will have a local DNS server available, so computer names can be resolved to IP addresses regardless of whether NetBIOS is enabled. In a peer to peer environment without a local DNS server (you could install one if you wanted to), you can use NetBIOS broadcasts to resolve computer names to IP addresses. If you don't have DNS and you don't have NetBIOS, you could use a hosts file - but if you don't have that either, then there is no way for computers to find each other by name. 3. Browsing: Browsing requires NetBIOS period. Even if computers exclusively use DNS or hosts files to resolve computer names to IP addresses, they will not be able to browse (My Network Places, Windows Explorer, etc.) unless NetBIOS is enabled. Doug Sherman MCSE Win2k/NT4.0, MCSA, MCP+I, MVP "James Egan" wrote in message ... On Thu, 22 Jul 2004 21:21:55 -0400, "Doug Sherman [MVP]" wrote: 2. Highlight TCP/IP and click the Properties button. Click the Advanced button and select the WINS tab. Either Default or Enable NetBIOS should be selected. If Disable NetBIOS was selected, that is the problem. Can you explain why it's the problem, please.? I know it resolved his problem, but I thought netbios was only required if the LAN contained win9x, winme or winnt machines. As both his machines are winxp, shouldn't they have been able to share files via port 445 using smb directly over tcp/ip without the need for netbios? Jim. |
#71
|
|||
|
|||
Network Setup Wizard
There are 3 related, but separate issues involved:
1. File Sharing: Craig was able to share files and he successfully did so without NetBIOS by connecting to the IP address of the machine. 2. Name Resolution: In order to connect to or share files with a computer by using its name, there must be some mechanism in place on the network which translates names into IP addresses. In a properly configured Active Directory domain environment all machines will have a local DNS server available, so computer names can be resolved to IP addresses regardless of whether NetBIOS is enabled. In a peer to peer environment without a local DNS server (you could install one if you wanted to), you can use NetBIOS broadcasts to resolve computer names to IP addresses. If you don't have DNS and you don't have NetBIOS, you could use a hosts file - but if you don't have that either, then there is no way for computers to find each other by name. 3. Browsing: Browsing requires NetBIOS period. Even if computers exclusively use DNS or hosts files to resolve computer names to IP addresses, they will not be able to browse (My Network Places, Windows Explorer, etc.) unless NetBIOS is enabled. Doug Sherman MCSE Win2k/NT4.0, MCSA, MCP+I, MVP "James Egan" wrote in message ... On Thu, 22 Jul 2004 21:21:55 -0400, "Doug Sherman [MVP]" wrote: 2. Highlight TCP/IP and click the Properties button. Click the Advanced button and select the WINS tab. Either Default or Enable NetBIOS should be selected. If Disable NetBIOS was selected, that is the problem. Can you explain why it's the problem, please.? I know it resolved his problem, but I thought netbios was only required if the LAN contained win9x, winme or winnt machines. As both his machines are winxp, shouldn't they have been able to share files via port 445 using smb directly over tcp/ip without the need for netbios? Jim. |
#72
|
|||
|
|||
Network Setup Wizard
There are 3 related, but separate issues involved:
1. File Sharing: Craig was able to share files and he successfully did so without NetBIOS by connecting to the IP address of the machine. 2. Name Resolution: In order to connect to or share files with a computer by using its name, there must be some mechanism in place on the network which translates names into IP addresses. In a properly configured Active Directory domain environment all machines will have a local DNS server available, so computer names can be resolved to IP addresses regardless of whether NetBIOS is enabled. In a peer to peer environment without a local DNS server (you could install one if you wanted to), you can use NetBIOS broadcasts to resolve computer names to IP addresses. If you don't have DNS and you don't have NetBIOS, you could use a hosts file - but if you don't have that either, then there is no way for computers to find each other by name. 3. Browsing: Browsing requires NetBIOS period. Even if computers exclusively use DNS or hosts files to resolve computer names to IP addresses, they will not be able to browse (My Network Places, Windows Explorer, etc.) unless NetBIOS is enabled. Doug Sherman MCSE Win2k/NT4.0, MCSA, MCP+I, MVP "James Egan" wrote in message ... On Thu, 22 Jul 2004 21:21:55 -0400, "Doug Sherman [MVP]" wrote: 2. Highlight TCP/IP and click the Properties button. Click the Advanced button and select the WINS tab. Either Default or Enable NetBIOS should be selected. If Disable NetBIOS was selected, that is the problem. Can you explain why it's the problem, please.? I know it resolved his problem, but I thought netbios was only required if the LAN contained win9x, winme or winnt machines. As both his machines are winxp, shouldn't they have been able to share files via port 445 using smb directly over tcp/ip without the need for netbios? Jim. |
#73
|
|||
|
|||
Network Setup Wizard
Thanks for the reply, Doug.
1. Firewalls on both machines are disabled. 2. Both computers are in same workgroup - confirmed. 3. User acct established on XP Pro machine that is identical to user on XP Home machine. Craig -----Original Message----- Try: 1. Make sure the firewall is not enabled on the XP Pro machine. 2. Make sure both computers are in the same workgroup - System properties/Computer name tab. 3. Create a user account on the XP Pro machine.which matches the user name and password used to log onto the XP Home machine. If you don't use a password in XP Home, create one or we'll have to change more settings. Doug Sherman MCSE Win2k/NT4.0, MCSA, MCP+I, MVP "Craig" wrote in message ... Hello all; I have two computers I'm trying to network. The laptop is running XP Pro and is connected driectly to a router. The desktop is running XP Home and is also connected directly to the router. Both machines work well with the Internet, so I don't suspect a problem with the router. I was able to use Network Wizard to create a home network with the laptop. After the network was created, I was able to use Windows Explorer to "see" the laptop on the the network including any shared files and printers. Now comes the problem. When I try to connect the desktop to the netwok using Network Wizard on that machine, Windows Explorer on either machine CANNOT see or find the desktop. Apparantly, Network Wizard on the desktop did not work properly for some reason. Can anyone help?? Craig . |
#74
|
|||
|
|||
Network Setup Wizard
Ok, we need to determine whether this is just a browsing issue or something
mo 1. On the XP Pro machine open a command prompt and type ipconfig ENTER. 2. Write down the machine's IP address, type exit ENTER. 3. On the XP Home machine, open a command prompt and type ping XP'sIPaddress ENTER. 4. If you get a response with no packet loss, we know there is connectivity. If ping fails, there is a firewall or problem with TCP/IP configuration. 5. If ping worked, then on the XP Home machine click Start Run; \\XPproIPaddress\c$ You should either get an Explorer window showing the files on the XP Pro's C: drive or a logon window. If you get the logon window, enter an XP PRo adminstrator's user name and password. If instead of the above, you get an error message, the XP Pro machine is not creating administrative shares. On the XP Pro machine, go to Administrative Tools/Services and try restarting the Server service. Check Event Viewer for error. Report back. Doug Sherman MCSE Win2k/NT4.0, MCSA, MCP+I, MVP "Craig" wrote in message ... Thanks for the reply, Doug. 1. Firewalls on both machines are disabled. 2. Both computers are in same workgroup - confirmed. 3. User acct established on XP Pro machine that is identical to user on XP Home machine. Craig -----Original Message----- Try: 1. Make sure the firewall is not enabled on the XP Pro machine. 2. Make sure both computers are in the same workgroup - System properties/Computer name tab. 3. Create a user account on the XP Pro machine.which matches the user name and password used to log onto the XP Home machine. If you don't use a password in XP Home, create one or we'll have to change more settings. Doug Sherman MCSE Win2k/NT4.0, MCSA, MCP+I, MVP "Craig" wrote in message ... Hello all; I have two computers I'm trying to network. The laptop is running XP Pro and is connected driectly to a router. The desktop is running XP Home and is also connected directly to the router. Both machines work well with the Internet, so I don't suspect a problem with the router. I was able to use Network Wizard to create a home network with the laptop. After the network was created, I was able to use Windows Explorer to "see" the laptop on the the network including any shared files and printers. Now comes the problem. When I try to connect the desktop to the netwok using Network Wizard on that machine, Windows Explorer on either machine CANNOT see or find the desktop. Apparantly, Network Wizard on the desktop did not work properly for some reason. Can anyone help?? Craig . |
#75
|
|||
|
|||
Network Setup Wizard
Hi Doug,
4. I pinged the XP Pro machine from the XP Home machine -- pinged ok with no packet loss. 5. \\XP Pro's IP Address\c$ returned the C: drive directory in a Windows Explorer window. I was able to move a file from the XP Pro machine to the XP Home machine, however, using the Windows Explorer on the XP Home machine, I still cannot "see" the XP Pro machine. Thanks again for your help. Craig -----Original Message----- Ok, we need to determine whether this is just a browsing issue or something mo 1. On the XP Pro machine open a command prompt and type ipconfig ENTER. 2. Write down the machine's IP address, type exit ENTER. 3. On the XP Home machine, open a command prompt and type ping XP'sIPaddress ENTER. 4. If you get a response with no packet loss, we know there is connectivity. If ping fails, there is a firewall or problem with TCP/IP configuration. 5. If ping worked, then on the XP Home machine click Start Run; \\XPproIPaddress\c$ You should either get an Explorer window showing the files on the XP Pro's C: drive or a logon window. If you get the logon window, enter an XP PRo adminstrator's user name and password. If instead of the above, you get an error message, the XP Pro machine is not creating administrative shares. On the XP Pro machine, go to Administrative Tools/Services and try restarting the Server service. Check Event Viewer for error. Report back. Doug Sherman MCSE Win2k/NT4.0, MCSA, MCP+I, MVP "Craig" wrote in message ... Thanks for the reply, Doug. 1. Firewalls on both machines are disabled. 2. Both computers are in same workgroup - confirmed. 3. User acct established on XP Pro machine that is identical to user on XP Home machine. Craig -----Original Message----- Try: 1. Make sure the firewall is not enabled on the XP Pro machine. 2. Make sure both computers are in the same workgroup - System properties/Computer name tab. 3. Create a user account on the XP Pro machine.which matches the user name and password used to log onto the XP Home machine. If you don't use a password in XP Home, create one or we'll have to change more settings. Doug Sherman MCSE Win2k/NT4.0, MCSA, MCP+I, MVP "Craig" wrote in message ... Hello all; I have two computers I'm trying to network. The laptop is running XP Pro and is connected driectly to a router. The desktop is running XP Home and is also connected directly to the router. Both machines work well with the Internet, so I don't suspect a problem with the router. I was able to use Network Wizard to create a home network with the laptop. After the network was created, I was able to use Windows Explorer to "see" the laptop on the the network including any shared files and printers. Now comes the problem. When I try to connect the desktop to the netwok using Network Wizard on that machine, Windows Explorer on either machine CANNOT see or find the desktop. Apparantly, Network Wizard on the desktop did not work properly for some reason. Can anyone help?? Craig . . |
Thread Tools | |
Display Modes | |
|
|