Workgroup with static ip, Win7, and legacy Windows system

[Pudding_Man]

Hi,

I have ATT DSL, 2-Wire (2701HG-B) router, 2 desktop systems hard-wired ethernet.
I am the only user.

When configured for non-static ip, problems with netbios "browsing" occurred. The router stays powered 24/7, but the pc's don't. I'd get the net working and MS Win would break it in a day or 2.

So I've set it up for static ip. I've been told that this will facilitate such a functional workgroup.

Ipconfig info on the 2 pc's follows my sig.

On the Win7 system and using Explorers Network icon, I get something like:

Enter Network Password
(for) System/User
x Logon Failure: unknown user name or bad password
OK Cancel

The "Failure" msg appears before -and- after I enter the Admin password. All the sharing options (i.e. file sharing) are turned on except password protection, which is "off". It is very similar using the W2k machine.

When I enter //192.168.1.2 from the Explorer-Address line
it brings up IE and sez "page cannot be displayed".

Such a simple, simple thing to ask of MS software facilities. I've tested it in more ways than I can shake a stick at. To date, nothing works for long.

Any ideas on how this can be done? I would cheerfully, cheerfully settle for a single shared folder.

Thanks,
P


--- PC1 - W2k sp4+ --------------------------------------------------------
Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : PC1
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1

--- PC2 - Win7-64 HP OEM -----------------------------------------------------
Host Name . . . . . . . . . . . . : PC2
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : gateway.2wire.net

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : gateway.2wire.net
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : XXXXXXXXXXXXXXXXXX
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.3(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Tuesday, November 23, 2010 1:18:29 PM
Lease Expires . . . . . . . . . . : Wednesday, November 24, 2010 Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.gateway.2wire.net:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : gateway.2wire.net
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : XXXXXXXXXXXXXXXXXX
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-00
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled
-------------------------------------------------------------------

[chrisbrown]

I've been at the pub for too long to answer your question correctly, but I will say it's not Microsoft's problem.

Also, if you want to browse, use a UNC path...ergo \\x.x.x.x\share

also, best to use the exact same set of credentials on both machines, this will allow for easy sharing.
As in...create the same account on both machines as a local admin.

[Pudding_Man]

I've been at the pub for too long to answer your question correctly, but I will say it's not Microsoft's problem.

No, it's not Microsoft's problem.

It is my problem.

But, my problem (in general) is .... Microsoft!

Also, if you want to browse, use a UNC path...ergo \\x.x.x.x\share

No help.

also, best to use the exact same set of credentials on both machines, this will allow for easy sharing.
As in...create the same account on both machines as a local admin.

I issued an identical user-ID on the Win7 machine. No help.

P

[Abaddon]

I believe he's referring to the fact that you've got your slashes the wrong way.. you say //, but for internal networks, it's \\.....

[strawberry]

we're doing pcworld out of work here lately

What are you actually trying to get the pc's to do? and when you "When I enter //192.168.1.2 from the Explorer-Address line" what are you hoping it will achieve?

[chrisbrown]

No, it's not Microsoft's problem.

It is my problem.

But, my problem (in general) is .... Microsoft!



No help.



I issued an identical user-ID on the Win7 machine. No help.

P

Well aren't you just a little ray of polite sunshine flowing into my Saturday morning.

Abaddon is right, I was referring to your using forward slashes instead of backslashes. If you have accounts with the same username and password on both machines, and they are local administrators, they will both have full and unrestricted access to each other remotely.

[Pudding_Man]

I believe he's referring to the fact that you've got your slashes the wrong way.. you say //, but for internal networks, it's \\.....

Thanks. I've been staring at this for too, too long. :-(

It still doesn't work. Prompts for apparently non-existant UID/password.

[Pudding_Man]

...

Abaddon is right, I was referring to your using forward slashes instead of backslashes. If you have accounts with the same username and password on both machines, and they are local administrators, they will both have full and unrestricted access to each other remotely.

Apologies for the previous.

There are identical user-ID's on each machine. Both are in the Admin group and have Admin privileges. And the 'private' profile sez do NOT prompt for UID/pw.

And it continues to prompt for apparently non-existant UID/password.

P

[SYNACK]

It is probably trying to append the computername to the authentication domain. In other words when you type in user on pc1 it sends pc1\user to the other machine by default.

Try adding the computername of the remote computer to the front of the username when you are trying to access the share ie: Username: remotePcName\username with the appropriate password.

You probably also have gues access turned off if you are looking to just logon to shares with no credentials. If this is the case you can enable this in the local group policy.

Despite the fact that your computer is effectivly trying to access the past this should still work as long as you are using the propper unc path \\server\share and the appropriate username.

Edit: here is a rundown on the compatibility concerns between systems using the Windows SMB/CIFS shareing system: http://support.microsoft.com/kb/823659

[Pudding_Man]

It is probably trying to append the computername to the authentication domain. In other words when you type in user on pc1 it sends pc1\user to the other machine by default.

Try adding the computername of the remote computer to the front of the username when you are trying to access the share ie: Username: remotePcName\username with the appropriate password.

Thanks. Didn't work, either direction.

On Win7, it echoed uid\pw, like pc1\firstname lastname after the 1st try, but it wouldn't log me on.

I think the "firstname lastname" user-id goes all the way back to NT4. Perhaps it doesn't know how to parse such?

You probably also have gues access turned off if you are looking to just logon to shares with no credentials. If this is the case you can enable this in the local group policy.

Despite the fact that your computer is effectivly trying to access the past this should still work as long as you are using the propper unc path \\server\share and the appropriate username.

Not certain I follow.

Edit: here is a rundown on the compatibility concerns between systems using the Windows SMB/CIFS shareing system: Client, service, and program incompatibilities that may occur when you modify security settings and user rights assignments

997 lines long. Aaaarrrggghhh!

Thanks,
P