Windows 2003 Share Headaches :(

[adlo]

I am using XP SP2 and need to access a windows share on server A (Windows 2003 Server). This server is on another domain as my laptop and has IP address 192.168.1.1. When I try to go to a server shared folder on my laptop I can't find it by selecting \\192.168.1.1 and get error the "network path was not found" when typing in the run command. I don't even get an authentication username and password popup.

However I can access windows shares on server B \\192.168.1.2 (i get the username and password popup) which is also WIndows 2003 server and on the same domain as server A and from what I can see the exact same setup as server A.

I can access the shared folders on 192.168.1.1 when I am remotely in 192.168.1.2 but not directly from my PC.
My IP is auto assigned and is in the 172 range.
My laptop is on setup on another domain than the servers and I am not connected to my domain but on the servers network.

I can remote desktop into both servers IPs.
I can ping both servers IPs
I can only access only the one server shares the other one gives me "network path not found."
Neither of the Servers or my machine have firewall enabled.
I can't access a windows share on my machine from both servers ie. this is exactly the same problem of accessing server A from my machine.

How can I access the folder share on the 192.168.1.1 directly or my laptop IP share from the server as I need to copy a file to my machine that is very large and can't copy from server A to server B to my machine due to size limitations on server B.

Any help?

 

[Dublin73]

This might be an obvious question, but are there any shares created on server A? Have you tried connecting to \\192.168.1.1\sharename (where "sharename" is the name of the share)

 

[adlo]

Yes there are shares created on server A. I said I can access the shares off server A from server B by typing 192.168.1.1. But I can't from my PC which is not on the same domain. Any PC on the same domain as server A can access its shares.

I can't change my domain.
How come I get path not found A at all when typing \\192.168.1.1 but I can ping it and remote desktop into it?

 

[Dublin73]

Have you tried mapping a network drive through Windows Explorer, using the "Connect using a different user name" option?

and when you type \\192.168.1.1\sharename what happens?

Have you tried accessing the share from a different client (on the 172 network)?

I presume you cannot ping server A by name, as you are trying to connect via IP address?

 

[adlo]

Yes I cannot ping server the by name but I can ping and remote desktop using IP.

When on other networks I have often accessed my machine from their server so it should not be a setup issue on my laptop.

I have been told that the machines on the 172 network that are on the domain can access the shares.

When I type in \\192.168.1.1\sharename i get a popup that prompts for an username and password (as opposed to getting nothing when typing in \\192.168.1) but whatever I put in the server A username and password field it just keeps on prompting me for the username and password despite me putting in a valid user. The user I am using is the administrator and has full share rights to that folder as it is the same user that I use when successfully accessing the folder when I access the share from remote desktop on server B or server A. I even created another admin user on server A just to confirm its not user related and the popup still prmompts me for username and password.

Windows firewall is setup on neither server or my laptop.

 

[Davetoo]

You have to enter the domain name first, i.e. domainname\username and then the password when prompted.

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.

 

[adlo]

I know that and I put in the domain name\username EXACTLY like I did for server B which worked but I still get prompted for a username and password which is the strange thing.
Why does this not come up directly when typing in \\192.168.1.1 and why does is just keep prompting? I am definitively putting it in correct and that user definitively has access to that share.

 

[Davetoo]

Remote into that server and check the event logs.

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.

 

[adlo]

There is no failed log in attempts in the security logs and nothing in the application or system logs.

 

[Dublin73]

it's odd that you're getting prompted to enter login credentials, but you don't see any errors in server A's event logs.

Have you tried putting your PC onto the 192 network (and tried to connect to server A) as part of your troubleshooting?

 

[adlo]

I have tried to set my IP address set on the 192 network but then I can ping neither 192 machines nor 172 machines.

I cannot put my machine on the domain as this is not my network and I must keep my current profile i.e. Outlook mail etc which is on my office domain and I am currently offsite.

 

[adlo]

The other server 192.168.1.14 is doing the exact same thing as server 1 i.e. I can access the shares

I can't find what is so special about the one server ( ) that works when I type in \\192.168.1.2 and whos whares I can access. All the servers are 2003 SP1 and no firewall.
I looked at all the permissions but cannot find any difference at all

I am tearing my hair out as I can't figure what is causing this.

 

[m1ckG]

Hi,

Have you tried using the net use command to try to map a connection to serverA.